[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Dragora-bug] Unify Dragora 2.x dragbuild script
From: |
kaltorak |
Subject: |
[Dragora-bug] Unify Dragora 2.x dragbuild script |
Date: |
Sat, 3 Aug 2013 10:50:01 -0400 |
Hi dragorians, I was trying to build some upgrades to D2 (Dragora 2.x)
packages, and usually I found that the difference between dragbuild-32 and
dragbuild-64 scripts are just the ARCH (i486 or x86_64) variable and the
library directory (lib for 32 bits and lib64 for for 64 bits) I found that a
little use of some coreutils commands like uname and the information provided
by /proc/cpuinfo allow to autodetect architecture at runtime, and some bash
lines to set up properly the library directory. I have a code prototype, based
on some scripts the selk provides
case "$(uname -m)" in
i?86) export ARCH=i486
BANDERAS="-march=i486 -mtune=i686"
;;
x86_64) export ARCH=x86_64
BANDERAS="-mtune=generic"
SUFARQ=64
;;
*) export ARCH=$(uname -m)
esac
Then for the library directory
./configure \
--prefix=/usr \
--datarootdir=/usr \
--sysconfdir=/etc \
--libdir=/usr/lib${SUFARQ} \
--libexecdir=/lib \
--build=${ARCH}-dragora-linux-gnu
It can be improved if we think in cross compilation, maybe we can add arguments
checking to the script for setting up the architecture.
Is just an idea, to your consideration. What do you say ?
PD: I post this message in a the new dragora wiki(thanks to blagora / kelsoo),
will be good if we use that space for discussion about Dragora.
This is the topic link
https://we.riseup.net/dragora/unify-dragora-2-x-dragbuild-script+206267
And this is the wiki link
https://we.riseup.net/dragora
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Dragora-bug] Unify Dragora 2.x dragbuild script,
kaltorak <=