#2 Library for stack and seperate visual studio projects

[Anonymous]

From my point of view it will be better to seperate
the protocol stack and the port or demo project in
different visual studio projects. For that reason the
usage of the protocol stack will be easier.

1. visual studio project: protocol stack

-> build a library that can be used in other projects

2. visual studio project: demo or application

-> use the library
-> include only the "interface" header files from the
protocol stack (from special directory)

You can include both projects in one visual studio
workspace.

please remeber to relative paths

[Edward Hague]

If anyone cares, I intend to add MSVC 2013 support very soon. There is a solution, with multiple projects - one for 'demo' another for 'library' and multiple for the example .exe standalones. Property sheets are used to control the options (e.g. BACFILE) that need to be set for all projects.