Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

Changes for autotools builds planned

(1/6) > >>

mandrav:
There are a couple of changes planned for autotools-based builds. They 're already implemented and working here for me but I will not commit them just yet because I won't be available during this weekend and so I wouldn't be able fix anything that may go wrong.

[*] update-revision.sh will update the version-revision in the debian/changelog too so generated packages will have the correct name (in case you didn't know, update-revision.sh should be run after 'svn update' and before 'make clean-zipfiles').

[*] The configure option '--enable-contrib=[yes|no]' is now obsolete. It has been replaced by the '--with-contrib=[all | plugin names separated with comma]'. So now you have the chance to avoid building contrib plugins you never use.

[*] Building the debian packages will no longer generate a single codeblocks*.deb package. Instead, 4 packages will be generated: codeblocks (main package), codeblocks-contrib (contrib plugins), codeblocks-dbg (unstripped binaries of codeblocks for debugging) and codeblocks-devel (sdk headers and libraries).
[/list]

That's about it. These changes will probably be committed on coming Monday.

Biplab:
Thanks a lot for the update. :D

Waiting for the commit.

mandrav:
Seeing no comments, I guess there are no objections :).

Another thing I 'd like feedback on is this: should one codeblocks-contrib package be created or one package per contrib-plugin? What do you think?

PsYhLo:
put POLL and will see :)
i'm for one codeblocks-contrib

raph:
I'm for one codeblocks-contrib package, too.

Navigation

[0] Message Index

[#] Next page