Some examples still depend on freespace_codecs and freespace_printers

[Dan Rinkes]

Building the examples with version 0.6 of libfreespace fails because the examples still @include the freespace_codecs.h and freespace_printers.h headers. None of the examples actually call any of the codecs APIS, but there are four that call the freespace_print function.

These are:
communication_example
motion_example
motion_example_async
multiple_device_example.c

Additionally, the freespace.h file in release 0.6 also #includes freespace_codecs.h.

Links:
trunk version of freespace.h
http://bazaar.launchpad.net/~libfreespace-devteam/libfreespace/trunk/view/head:/include/freespace/freespace.h

trunk version of common folder (used to contain the _codecs.c and _printers.c file but no longer does.
http://bazaar.launchpad.net/~libfreespace-devteam/libfreespace/trunk/files/head:/common/

[Dan Rinkes (dan-rinkes)]

The issue here is really that the mentioned files are automatically generated when running the winbuild.bat script. This should be better documented because the first impression to customers is likely to be that there are files missing from the release.

[Khalid Zubair (kzubair)]

The README.win32 doesn't do a good job describing these dependencies. I think it needs to be documented there.

In my opinion winbuild.bat should not be running the messageCodeGeneator. It should be one of the build steps in each of the the Visual Studio projects.

The Linux autoconf setup handles this a lot more elegantly.