...
- Figure out what needs to be in a library project file to get Studio to copy the library to the SCons variant lib directory (same place the library gets installed when built by SCons). Done
- Get SCons to create a usable environment-setter-upper, probably a .bat file that can be run before invoking devenv.
Wiki Markup Currently only .cxx files are added to projects. Need .h, possibly also xml, python, etc. _\[3/11 update: will go for scheme similar to what's done now in CMT requirements. Package maintainer will be responsible for specifying these files in the package's SConscript file\]_
- The .cxx files in the project are specified using an absolute file path. This allows Studio to find the files, but means that the project files are not portable. They must be built where used. Should either** figure out how to express path in terms of an environment variable which translates to the root of the container. This environment variable then needs to be defined when the setup file is run.
Wiki Markup _or_ make a special SCons target for an installation which only regenerates all project and solution files. _\[3/11 update: will go for this one\]_
- Don't know how to make a solution file referencing all the projects in a package. When I try the obvious thing from within SCons, invoking MSVSSolution( ), the resulting file uses paths to the SCons build area rather than real destination of the file. The ones in the build area are not (and are not intended to be) usable as project files. When I tried adding a second project to a solution file from within Studio it balked.
- Is it possible to encode dependency information of one project on another in a project file? If so, get SCons to add this information to the project files.
...