(sent using wrong email address, trying a resend. sorry if I break your email client threading)
On 3/3/07, Chris Frey <[EMAIL PROTECTED]> wrote: > > I don't really care to put system specific stuff in the makefiles > when, in my opinion, this stuff probably belongs in the binary packages > anyway. Fair enough, I'm taking care of it during packaging. > I'm surprised you need CXXFLAGS, etc. Does this add to the existing compile > flags or replace them? For the GUI it shouldn't matter, but when compiling > the library, it is important that -fno-strict-aliasing is set. It adds to them. Well, there are various methods to use but the way I do it is an additive approach. I am specifically seeing -fno-strict-aliasing during the builds. A hard -rpath ../ is not included, it just sorta all works out. > The main dependencies are listed in the GUI README, and those dependencies > themselves (gtkmm, glibmm, etc) have fairly large subdependencies. I'm with you -- I took a modularized approach so it should work out. It's at least not throwing errors so far, but I'm the design/build system. :) Of course I have all the right things installed now; we'll have to let a poor end-user QA for me. > libtar doesn't have pkg-config support on some of the systems I've put it > on (Debian stable for instance), so this check would need special configure.ac Fair enough, I just added it as a BuildRequires for -gui subpackage; I named it -gui to make it match other things -- like beagle, libbeagle and beagle-gui for instance. That way we can add more/newer gui apps later and the package name stays generic. Future-proof. > > A) Create one SPEC file to rule them all. The spec file would require > > I like this option merely for the fact that when updating things, it will > be harder to forget things if it's all in one place. I have gone this route; there can be only one, highlander. I've got a clean compile (step #1), the rest is to clean up (like add that hotplug, examine for missing docs, etc.) and test. I'll upload it to the Patches section when done. I backported a RPM macro from rpm-4.4 into the barry.spec so that this can compile (I hope!) on CentOS/Red Hat Enterprise 4 systems, which have rpm-4.3. Wrote: /usr/src/redhat/SRPMS/barry-0.6-1.src.rpm Wrote: /usr/src/redhat/RPMS/i386/barry-0.6-1.i386.rpm Wrote: /usr/src/redhat/RPMS/i386/libbarry-0.6-1.i386.rpm Wrote: /usr/src/redhat/RPMS/i386/libbarry-devel-0.6-1.i386.rpm Wrote: /usr/src/redhat/RPMS/i386/barry-util-0.6-1.i386.rpm Wrote: /usr/src/redhat/RPMS/i386/barry-gui-0.6-1.i386.rpm Wrote: /usr/src/redhat/RPMS/i386/barry-debuginfo-0.6-1.i386.rpm 'barry-opensync' is in the SPEC (--with opensync), but because I can't get a good compile (and really, no ./configure yet) I'm not exercising it's usage. It's mainly a copy of -gui, not a whole lot can go wrong when we get there. All subpackages require 'barry', which contains nothing more than the GPL license, README, etc. - I figure it was a good way to compartmentalize the generic docs and not clutter every single package with them. This also ensures the user has to install the license and README. :) We can break out the doxygen/ later when it's ready into a barry-doc or whatever. $ rpm -qlp /usr/src/redhat/RPMS/i386/barry-0.6-1.i386.rpm /usr/share/doc/barry-0.6 /usr/share/doc/barry-0.6/AUTHORS /usr/share/doc/barry-0.6/COPYING /usr/share/doc/barry-0.6/ChangeLog /usr/share/doc/barry-0.6/Exceptions /usr/share/doc/barry-0.6/Hacking /usr/share/doc/barry-0.6/NEWS /usr/share/doc/barry-0.6/README /usr/share/doc/barry-0.6/ReleaseChecklist.txt /usr/share/doc/barry-0.6/TODO /usr/share/doc/barry-0.6/TimeZones.txt /usr/share/doc/barry-0.6/USB-capture.txt /usr/share/doc/barry-0.6/VersionNotes /usr/share/doc/barry-0.6/doxygen /usr/share/doc/barry-0.6/doxygen/.cvsignore /usr/share/doc/barry-0.6/doxygen/README -te -- some live, some die in the way of the samurai ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
