LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   .SlackBuild optimize compile, need help (http://www.linuxquestions.org/questions/slackware-14/slackbuild-optimize-compile-need-help-185430/)

chemtraX 05-24-2004 09:38 PM

.SlackBuild optimize compile, need help
 
currently i'm downloading *almost* all slackware's source in /a directory and study everything in the program_name.SlackBuild script.I'm thinking of making my own optimized slackware packages.

my question, is it enough for me to put this flags in root's .bashrc file
Code:

CFLAGS='-O2 -march=i686 -mcpu=athlon-xp -pipe'
CXXFLAGS="$CFLAGS"
export CFLAGS CXXFLAGS

chmod +x program_name.SlackBuild, run it as root and the program_name.SlackBuild will yield the *.tgz package optimized for my athlon-xp cpu?or i need to use slackbuilds package from linuxpackages.net?

can somebody help me? thanks... :)

thegeekster 05-25-2004 02:39 AM

Yes, you can place it there, or you can put it in a "slackbuild.options" file, along with other variables needed for making pkgs, then source that file with each SlackBuild script like this:

. /etc/slackbuild.options

I'm currently in the same process of setting up my own build system, following the examples from various sources: LinuxPackgaes.net, Slackware, and LFS/BLFS (Linux From Scratch / Beyond Linux From Scratch)

I've elected to put the options files (including a separate one especially for KDE, called KDE.options) in the /etc directory, to be consistent with the Slackware setup of using /etc for configuration files

While I still have those variables in my startup script, I'm thinking of removing them as soon as I complete my package building system, so far I have KDE/QT fine-tuned to the point where I'm satisfied, but I still have my work cut out for me with the configure options for the rest of the Slackware source tree, including the extra/source/ directory...........There are still some old build scripts that do not follow the relatively recent buildscript naming convention of "package_name.SlackBuild", which I will be converting.................Also, I've created a "template.SlackBuild" file to help make the job easier, but it will still take some time to finish the project (and keep me out of trouble ;)).................The template will also help with any third-party apps that I eventually want to build and use....

If you need help with some specifics, let me know :)

gargamel 05-25-2004 03:21 PM

Would you think you'd be prepared to make your build system publicly available once it is finished?
Possibly as an open source project, hosted eg on Sourceforge?

I really think there's quite some interest in this subject --- I guess this from the many threads on "Gentoo vs Slackware" and "how to optimise my Slackware build". Obviously there are a few Slackware users who want to optimise with a little more comfort than is available right now, but not switch distribution.

Regards

gargamel

chemtraX 05-25-2004 05:17 PM

no...i will keep the packages for myself..since i'm totally a newbie,this is just for the sake of learning..it wont be any great..
slackware is slackware..keep it that way.. :)

slackware really force me to learn.. :D

thegeekster 05-27-2004 05:09 PM

Quote:

Originally posted by gargamel
Would you think you'd be prepared to make your build system publicly available once it is finished?
Possibly as an open source project, hosted eg on Sourceforge?

I really think there's quite some interest in this subject --- I guess this from the many threads on "Gentoo vs Slackware" and "how to optimise my Slackware build". Obviously there are a few Slackware users who want to optimise with a little more comfort than is available right now, but not switch distribution.

Regards

gargamel

As for me, I've given it some thought, but not much........it will take some time to complete, maybe another month or two, since I will need to juggle my time and test everything..................And I never even thought about SourceForge.......... ;)

I've seen some of the build scripts others have on the 'net, but nothing so complete as to allow a user to completely rebuild Slackware from source, which is what I have in mind......................I agree Slackware could use a bit more in that department, but I also agree with the Slackware "do-it-yourself" philosophy..............Therefore, what I'm doing will use the current tools available to Slack........and anyone else should be able to devise their own system with a little knowledge of shell scripting, which is why I've only given it minimal thought since anyone can do the same thing...........

If I thought this is something others truly want, then yes, otherwise I can't see justifying wasting space at SourceForge.........................there's already too many abandoned projects cluttering the scene over there, if you catch my meaning, and if it's something that's not going to be popular, then why bother setting the project in motion, only to have it bomb out and wasting space for something more deserving.......*shrugs*


All times are GMT -5. The time now is 01:13 PM.