I distribute the .rc file in the tarball in order for the MSC build system to be able to use it. Had we supported only one build system (autoconf) we could have avoided this and produce much cleaner solution. I can remove all the generated files from the tarball if they are not used anywhere.
On Mon, Feb 1, 2010 at 5:34 PM, Andreas Jellinghaus <a...@dungeon.inka.de> wrote: > Am Montag 01 Februar 2010 16:28:46 schrieb Andreas Jellinghaus: >> there is this central >> versioninfo.rc file in win32. but src/libopensc/ has a versioninfo.rc >> code in Makefile.am too. strange. and some apps are linked with >> versioninfo.rc, but not all (test, scconf, common, ... might be >> missing the code to do that). >> >> but with little clue about windows build (mingw or visual studio), >> I can't help much here. >> >> I saw some builddir vs. sourcedir bugs, will fix them. > > nah, I better don't as I don't understand the code. > > libopensc/Makefile.am for example: for win32 the > versioninfo.rc is part of _SOURCES. Thus it is generated > with the rule at the end, placed in *.tar.gz files > (also on linux via the dist_noinst_DATA hook). and it > is cleaned up on maintainer-clean from $srcdir. > fine so far. > > but what about CLEANFILES? it would clean the versioninfo.rc > from builddir? but if builddir == srcdir, it would clean it > there too? why? and the versioninfo.rc: code creates the > file in builddir? shouldn't it be created in srcdir instead? > or both? > > I'm confused as you can see, not sure what the intention > with the file exactly is. Alon, can you help? > > Regards, Andreas > _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
