I am thinking, what would be the best way for me to keep current with the latest code that is also tested to build on Windows?
If I understood your development cycle correctly, you make changes, test them on Linux, commit to 'develop', wait till the nightly Windows build, then make new changes if something went wrong with Windows and commit them again to 'develop'. Could you have any way to mark the commits that were known to work on Windows? Maybe a branch or a tag?
Thanks,
Andrey
-----Original Message-----
From: [">mailto:] On Behalf Of Ben Webb
Sent: Thursday, April 04, 2013 11:37 AM
To: Help and discussion for users of IMP
Subject: Re: [IMP-users] Windows build
On 4/4/13 12:14 AM, Tovchigrechko, Andrey wrote:
> These were causing C++ syntax errors on Windows. Looking at those, it
> appears that things currently get committed into the 'develop' before
> they are checked for being able to compile on Windows natively. Is
> that a policy matter?
I don't understand what you mean here. We certainly don't have an anti-Windows commit policy. ;) But we generally develop on Linux/Mac, so don't see problems with MSVC builds until our nightly builds run.
> setup_environment.bat needs Release (or Debug) appended to paths after
> "bin" and "lib" (that one I did not fix in the code)
Hmm, that's odd - maybe a cmake bug - it's not necessary for nmake builds. I guess Visual Studio builds put the outputs in the wrong place.
What version of Visual Studio are you using?
Ben
--
http://salilab.org/~ben/
"It is a capital mistake to theorize before one has data."
- Sir Arthur Conan Doyle
_______________________________________________
IMP-users mailing list
https://salilab.org/mailman/listinfo/imp-users