|
From: Frank V. C. <fr...@co...> - 2000-09-01 00:57:31
|
Yes, this is where I had the problem. My work around was to do a make install-includeHEADER as the target for include/clfw so it only put the two files, and then add another install line for LibLoad. If you look at the %install section of the spec you will see what I mean. See, now I am dangerous :) Christophe Prud'homme wrote: > > Hi > Now clfw has its own debian packages > but > the .h go in /usr/include/cflfw > shouldn't it go to /usr/include/cflfw/LibLoad or something like that? > > I'll have a look at the spec file to get the same directories framework > > C. > -- > Christophe Prud'homme | > MIT, 77, Mass Ave, Rm 3-243 | Un prud'homme était un homme > Cambridge MA 02139 | d'honneur et de valeur, > Tel (Office) : (00 1) (617) 253 0229 | sage et loyal. > Fax (Office) : (00 1) (617) 258 8559 | -- Chateaubriand > http://augustine.mit.edu/~prudhomm | > Following the hacker spirit > _______________________________________________ > Corelinux-develop mailing list > Cor...@li... > http://lists.sourceforge.net/mailman/listinfo/corelinux-develop -- Frank V. Castellucci http://corelinux.sourceforge.net OOA/OOD/C++ Standards and Guidelines for Linux http://PythPat.sourceforge.net Pythons Pattern Package |