On Sun, Mar 04, 2007 at 01:47:18PM -0800, troy engel wrote: > (sent using wrong email address, trying a resend. sorry if I break > your email client threading)
It worked fine. First of all, Thanks! This is a great benefit, and should make version 0.7 the first release with binary RPM's included for Fedora 5 and 6. Comments below: > > 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. Excellent, glad to hear it. > > 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. It's working great here on Fedora 5... will test with 6 shortly. The idea is to put binary releases on the file download page, so hopefully only developers or people with different architectures will need to build the RPMs. > > 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. Sounds good. I wasn't aware of the -gui convention, so I'll agree with that. > 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. I've tested the build on a RHEL4 system just now, and rpm-4.3 chokes on the %if statements for some reason. I also had to tweak the autoconf scripts a bit to get it to compile, as it needs libusb explicitly given on the command line. Once that was done (the autoconf fixes are in CVS), I removed the gui and opensync parts of the spec file, and it built fine. So we just need a fix or workaround for the %if statements. > '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. Yes, opensync isn't ready yet. It's only half coded at this point. > 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. I didn't like the barry base package, as it seemed a bit wasteful to me, and we need the license in every package anyway. Since libbarry is really the common package that all the others depend on, I've moved the common documentation files there, and moved some of the more techy ones into libbarry-devel. I'll commit my changes into CVS soon, and if you have more comments, please let me know. Thanks again! - Chris ------------------------------------------------------------------------- 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
