Fix build by removing auto generated files#75
Conversation
Files generated by flex or autotools should not be stored inside repository. This may lead to compilation errors as reported by a few users. Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
|
Removing the auto**** generated files from a VCS is usually a real pain if you just want to build it; eg: for testing on your unusual setup. You end up having to hunt down the exact version of auto**** that the input files were written for because auto****'s upgradability is so poor. I would suggest a better solution is to keep the generated files in the repository in such a way that
Note the last one MUST generate then save so that when the version of auto**** is too different the (probably) working scripts are not deleted. BTW: This isn't a dig against the scripts that auto**** generates they are normally very, very, portable it's just that those are what you're supposed to run on the varied target machines, not As for the Edit: distclean not clean |
|
I'm OK with removing these files from the repo. I've already removed the scanner.[ch] and grammar.[ch], however the problem with those is that Windows developers will have no way to regenerate these files, because the Visual Studio solution doesn't have rules to regenerate them with flex and bison, the assumption being that the typical Windows developer wouldn't have these tools installed. So I may end up putting those files back in. |
|
All the autotools files are removed, but I left the flex- and bison- generated files in the repo, for the benefit of Windows developers. It isn't a problem to have these in the repo as long as we ensure that they are kept up to date with respect to the .l and .y files. |
Remove auto generated files to prevent build failures.
Everything can be build using:
$ autoreconf -i
$ ./cofigure
$ make
This fixes issues: #66 #61 #53