Code::Blocks Forums
User forums => General (but related to Code::Blocks) => Topic started by: LonelySTar on November 30, 2005, 01:37:59 am
-
Hello together,
Is it possible to export a project into a automake like tar file? So that the packet can bes installed doing:
tar xvzf ...
./configure
make
make install
???
Thanks,
Nathan
-
Mmhh ... It says, that with the new version, C::B uses automake for non-windows platforms (I am using Linux). But I can not find any automake files in the project directorie...???
-
The source distribution of codeblocks for linux uses automake to build install it. When installed you can forget autotools, codeblocks generates command line arguments for the compiler and invokes it one command at a time.
-
And you can generate a makefile.
-
And you can generate a makefile.
Isn't that disabled in current SVN because it was way outdated and didn't work properly anymore?
-
I have somewhere read of a scons plugin. Does it exist?
-
I have somewhere read of a scons plugin. Does it exist?
http://forums.codeblocks.org/index.php?topic=593.msg3712#msg3712
and
http://forums.codeblocks.org/index.php/topic,489.0.html
Not a plugin, tho.
-
Mmmh ... ok. Is anybody doing a cross-platform project distributed as source here?
I mean, I have a atotoolset project, and a I am thinking of using C::B. Is there an elegant way?
-
Well, there's Code::Blocks itself, of course. Only available as source and Windows binaries. Unfortunately they don't use autotools in any elegant way as far as I can tell, they just update the files manually (and, as it seems from reading the Unix/Linux boards, usually a bit late Rolling Eyes)...
Unfortunately they don't use autotools in any elegant way as far as I can tell, they just update the files manually (and, as it seems from reading the Unix/Linux boards, usually a bit late :roll:)...
-
Unfortunately they don't use autotools in any elegant way as far as I can tell, they just update the files manually (and, as it seems from reading the Unix/Linux boards, usually a bit late :roll:)...
Urxae: That gives me a GREAT idea! How about adding, besides "generate makefile", a "generate autotools files"?
P.S. I was supposed to quote you but it seems i messed up and edited YOUR post instead. Sorry :oops: but it's fixed now.
-
Unfortunately they don't use autotools in any elegant way as far as I can tell, they just update the files manually (and, as it seems from reading the Unix/Linux boards, usually a bit late :roll:)...
:|
-
Unfortunately they don't use autotools in any elegant way as far as I can tell, they just update the files manually (and, as it seems from reading the Unix/Linux boards, usually a bit late :roll:)...
Urxae: That gives me a GREAT idea! How about adding, besides "generate makefile", a "generate autotools files"?
I was thinking after I posted that: "that might be an idea for a plugin, though"...
P.S. I was supposed to quote you but it seems i messed up and edited YOUR post instead. Sorry :oops: but it's fixed now.
hehe... no problem, looks intact except for the 'edited by rickg22' part :).
Unfortunately they don't use autotools in any elegant way as far as I can tell, they just update the files manually (and, as it seems from reading the Unix/Linux boards, usually a bit late :roll:)...
:|
Not that I personally mind, I use C::B itself to compile anyway.
Just my conclusions drawn from the forum spamming generated whenever files are added to the project...
Feel free to consider it motivation to automate this through a plugin or C::B change though ;). Or perhaps to make it part of the big compiler plugin overhaul you guys have planned post-1.0 if that'll work out better.