Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Changes for autotools builds planned
anarxia:
Just a few comments for the debian directory:
1. You basically hardcoded all dependencies. That's a big no-no for several reasons. You should use ${shlibs:Depends}.
I can fix the packages to work correctly with ${shlibs:Depends} if you are interested and send a patch here.
2. The -devel prefix is -dev in the Debian/Ubuntu world.
3. You can build-depend on a specific version of libstdc++-dev, but you should also provide | libstdc++-dev as an alternative for people with
other versions of g++.
4. You shouldn't install the .la files. All library packages remove those as they cause problems.
mandrav:
--- Quote from: anarxia on July 17, 2007, 05:07:52 am ---Just a few comments for the debian directory:
1. You basically hardcoded all dependencies. That's a big no-no for several reasons. You should use ${shlibs:Depends}.
I can fix the packages to work correctly with ${shlibs:Depends} if you are interested and send a patch here.
2. The -devel prefix is -dev in the Debian/Ubuntu world.
3. You can build-depend on a specific version of libstdc++-dev, but you should also provide | libstdc++-dev as an alternative for people with
other versions of g++.
4. You shouldn't install the .la files. All library packages remove those as they cause problems.
--- End quote ---
Thx for the comments. Patches are welcome ;)
mandrav:
--- Quote from: dmoore on July 16, 2007, 04:29:46 pm ---Mandrav: is there a wiki entry explaining how to use these things correctly? (even just command lines and required packages for deb/rpm systems)
--- End quote ---
These are the generated packages (if one would build them). For installing them, use your distro's package manager(e.g. synaptic, dpkg, etc).
Also, there are dependencies between them so you can't, for example, install the 'codeblocks' package without first installing 'libcodeblocks0'. Your package manager would either install the dependencies automatically or, at the worst case scenario, tell you about what's missing.
Finally, the -dev(el) packages are only needed if you want to use the C::B SDK (w/out having C::B in source form available).
Charon:
that looks quite nice :)
personally i think i would split the contrib plugins up into a few packages, but create a meta-package which references all of them.
the dev-package is a great idea btw!
greets
Markus
dmoore:
--- Quote from: mandrav on July 17, 2007, 02:02:43 pm ---These are the generated packages (if one would build them)
--- End quote ---
yes, I want info on building the packages correctly (as opposed to installing them). I asked about dependencies because I assume that to build the packages there are several tools required (such as debhelper). I never did manage to create the deb package with the old setup and I figure I'm not the only person who would be interested in having this info in a readily accessible place
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version