Am 09.05.2011 um 06:35 schrieb Fabian Buske:
Hi, I like the new structure of seqan. Below are, however, a couple of things I notices on Macs (with Xcode).1.) When following the tutorial for "getting started" and jumping rightto the Mac section and following from there I noticed that the "forwards" are not generated when opening the sandbox and trying to compile the example resulting in plenty of compiler errors. # mkdir Debug # cd Debug # cmake ../.. -DCMAKE_BUILD_TYPE=Debug -G "Xcode" # open sandbox/my_sandbox/seqan_sandbox_my_sandbox.xcodeproj or # open core/demos/seqan_core_demos.xcodeproj Opening the overall project build/Debug/seqan.xcodeproj and compiling anything at all first seems to be a workaround to get the "forwards" generated.
Did you use the skel generator script or the zip file with the example sandbox? I remember that there were some issues with the generator that I fixed in [9570]. I forgot to update the ZIP file in the tutorial and just did this.
2.) Running the cmake command after populating the app folder does not seem to pick up additional header files in an app. cmake ../.. -DCMAKE_BUILD_TYPE=Debug -G "Xcode"3.) The same seems to be true for the sandbox tests. Here neither header nor cpp files dropped into the sandbox/test/testapp-folder are picked upby cmake.
Did you look into the existing apps and tests? Headers have to be added manually to the seqan command adding a new test/app executable.
Bests, Manuel