I've got a set of code in Crossworks that I am partioning off into libraries within the solution. Ultimately, I want to expose this code as a set of easy function calls to other users as a static library, without actually providing the source code.
The big idea is that I can pass off a basic Crossworks project and set of files to other Crossworks users along with the library of protected calls.
So far, it has been straightforward, but all I've done is create a library and move code into it from my main project. I have compiled and the library has been created, but this was done all within one solution (with two projects, the main calling code and the library) with all source visible. I would like to test it by switching to a configuration that does NOT compile the source and simply links to the library that was created.
Is there an easy way of creating a configuration that excludes the source files from the build, but links the library that was created? Or is it recommended that I have a separate solution that contains only the main code and links the library in?
Any suggestions in this area would be greatly appreciated...
Please sign in to leave a comment.