From: Michael H. <mic...@el...> - 2005-09-15 12:45:17
|
Milan, Damyan, Milan Babuskov wrote: >> 2) config-options make target fails: >> >> $ make config-options >> cp: cannot stat `./confdefs/fr_settings.confdef': No such file or >> directory >> cp: cannot stat `./confdefs/db_settings.confdef': No such file or >> directory >> make: *** [config-options] Error 1 >> (`make all' fails with the above errors, also. right after building >> flamerobin executable) > > FlameRobin has somewhat different build system. Since we support > different compilers and platforms from the same bakefile, some files > need to be copied. To make a long story short, you can't build in root > source directory, but need to make a subdirectory for it: Well, some would say that building in a subdirectory is not a bad thing for other reasons as well. But anyway, the build does in fact succeed even in the root directory, only copying the three subdirectories onto themselves does obviously fail. But then I'm not sure this copying needs to be part of the normal make target, as there are other ways now to make FR find its support files, and for making a release a distinct make target for copying the files would do. Milan, what do you think? > You should use --disable-shared and --disable-debug. Of course, you > should have also built wxWidgets with same flags. Some other > combinations might work, but I'm not sure about it. --disable-shared is for wx only, FlameRobin does not use this parameter, it gets the information about wx from wx-config. I don't think that mixing --enable-debug and --disable-debug would hurt, but one does either want to debug FR or not, so using the same setting makes sense. > --prefix=/usr/local. As I understand, this does not conform to Debian > guidelines, i.e. you would probably need --prefix=/usr. Currently, > the configure script does not update the sources, so you'll need to > manually edit the file: src/config/Config.cpp and change "/usr/local" > to "/usr" or whatever is needed. I'm working on that. I have in fact already a solution for the configure script (a header file gets created in the build directory), this needs only be integrated with the sources. But as I'm only trying to find my way around autoconf stuff - if you, Damyan, have more experience with this, your help to make that as standard as possible would be much appreciated. Thanks -- Michael Hieke |