Environment Extension - Static Libraries
Posted: 19 Apr 2010, 13:55
I'm currently looking into creating an environment extension for BCI2000 and I have a development issue.
Instead copying all the cpp files to my project I would like to link against a static library. To do this a .lib file should be build from the existing files. However I couldn't find which files I HAVE to include for this and before I turn to trial and error building, I would like to know your opinions. Both on the entire idea of building (a) static librar(y/ies) from BCI2000 that can be used in other programs and on what this lib should contain to function properly.
I am aware of the fact that this would require rebuilds when new versions appear, but if a new version of the C++, a rebuild is required anyhow.
Instead copying all the cpp files to my project I would like to link against a static library. To do this a .lib file should be build from the existing files. However I couldn't find which files I HAVE to include for this and before I turn to trial and error building, I would like to know your opinions. Both on the entire idea of building (a) static librar(y/ies) from BCI2000 that can be used in other programs and on what this lib should contain to function properly.
I am aware of the fact that this would require rebuilds when new versions appear, but if a new version of the C++, a rebuild is required anyhow.