When project contains only one .cpp or only one .h file, incorrect paths are generated. SConstuct file in attached zip [http://dl.dropbox.com/u/1777581/sconsbug.zip] generates two projects: project1 and project2. project1 contains only one cpp file: main.cpp. After opening generated project in Visual Studio and double clickin on main.cpp you will get error message. project2 is ok.
Hi -- we're still figuring out this bitbucket thing :-). A couple of things on this: your patch looks OK to me but we can't accept as is without a test to go with it (eventually a core dev will probably try to write a test so we can accept it, but if you can modify the existing test that will help hugely). The workflow we're trying to use is documented at http://www.scons.org/wiki/SconsMercurialWorkflows, and in there we're also encouraging pull requests on topic branches.
Hi! I'm trying to setup build workflow. I'm running
hg clone ssh://firstname.lastname@example.org/scons/scons
python bootstrap.py build/scons
but I get an error
Traceback (most recent call last):
File "bin/scons-proc.py", line 108, in <module>
TypeError: initial_value must be unicode or None, not str
scons: *** [build/doc/man/builders.man] Error 1
scons: building terminated because of errors.
Am I doing everything right? Can this be somehow fixed? Any temporary workaround?
Hi Alexey. The tests alongside the source files (e.g. src/engine/SCons/Tool/msvsTests.py) are unit tests; they test the detailed operation of the corresponding source file, usually by getting manipulating detailed state of the code under test; they don't do whole builds. The tests in test/ subfolders are system tests; they test black-box operation of the whole system usually by doing builds and seeing if the results (generated files, stdout/stderr) match expectations.
In most cases the unit tests don't require the tool (MSVS) to be installed; they just test whether things are set up correctly so the tool *should* run fine when given correct input. But the system tests can't run without the tool since they actually run it.
Hi, Gary. Finally I've made tests for this case. Sorry for a bit messy commit history because of TextMate project. Next time I will do separate feature branch according to a SconsMercurialWorkflow guideline. Or if you wish I can create a new "clean" pull request
Thanks -- this is looking better. Sorry for the python version confusion before. Would you mind cleaning it up? I think you can use the hg rebase or mq extensions (http://mercurial.selenic.com/wiki/EditingHistory) to do that easily. Just submit a new pull request and close this one (or I can), then we're ready to accept.