-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I took the Makefile.am files and added a few lines to each one which allows building as a framework.
In my 1.0.49 version I also made changes to fix/allow building in a build directory since this never worked properly. The framework also includes the cgilib so it's a one-stop framework I'd send you a diff but since I hacked the files to skip building the example stuff One thing I haven't fixed (not that it's important in the 1.0.49 version) is the 'rrdtool --help' or 'rrdtool --help <command>' in the rrdtool application (this has never worked that I am aware of) As well, it builds a tcl and python module for 1.0.49, I'd upload my modified 1.0.49 version for you to examine but I can't remember the ftp login information from the last time I uploaded something since it's been so long. I also have a framework.m4 file that allows you to test for frameworks and functions (a modified CHECK_LIBS routine)and I've been using a different but more mainstream approach to obtain file suffixes for shared libraries and modules. It currently takes: (I'd do a proper fix if I could get some info about other OS's) ./configure --enable-shared --with-tcllib=/usr/lib # location of tclConfig.sh - shared must be enabled because I was lazy and don't test make framework make install-framework To include the header file I use: #include <RRDTool/rrd.h> instead of: #include <rrd.h> To link: - -framework RRDTool instead of: - -L/lib/path -lrrd' I include a rrdConfig.sh file to aid in development. I did leave a method which allows a legacy include by creating a symlink in /$(prefix}/include to the header files and symlinks to the library files so anything that previously built without issue will continue to do so. Linking is done with -framework RRDTool' instead of -'L/lib/path - lrrd' and I include a rrdConfig.sh file to aid in development. I could do a much better job if I had some info about framework patchs and detection and I spent more time on it but hey, it was a quick fix and the end product is fantastic. - -- Dale On Aug 8, 2007, at 10:16:48, Tobias Oetiker wrote: > Hi Dale, > > can you tell me more ? currently it takes > > ./configure > make install > > but if there is a simpler way I would certainly be interested in > learning about it ... > > cheers > tobi > > Today D. Walsh wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> I've been generating a framework from RRDTool that seems to make >> linking and >> usage so much easier, I started with 1.0.49 (my favorite for it's >> simplicity) >> and now with 1.2.14, is this something that interests anyone as a >> project >> option? >> >> - -- Dale >> > > -- > Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten > http://it.oetiker.ch [EMAIL PROTECTED] ++41 62 213 9902 > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (Darwin) iD8DBQFGumJEgKKwRgpESgMRArL6AJwKEXEVs6tBQv7WhSzkP+HjQ5xgyQCfdhMk umbPHKT9Zm9NfbaSoB4FM58= =g+zI -----END PGP SIGNATURE----- _______________________________________________ rrd-developers mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/rrd-developers
