[opensource-dev] Hacking up to Visual Studio 2010 ...

Brandon Husbands xotmid at gmail.com
Fri Feb 18 08:51:24 PST 2011

Trying to build with vs2k10 pro

D:\Other\vd\viewer-autobuild>autobuild configure -c OpenSourceRelWithDebInfo
Configuration file 'D:\Other\vd\viewer-autobuild\autobuild.xml'
configuring in D:\Other\vd\viewer-autobuild\build-vc80
configuring for configuration(s) [{'default': False, 'configure':
{'command': No
ne, 'options': ['-G', '"Visual Studio 8 2005"', '-DSTANDALONE:BOOL=FALSE',
STALL_PROPRIETARY=FALSE', '-DFMOD=FALSE'], 'arguments': None}, 'name':
ceRelWithDebInfo', 'build': {'command': 'devenv.com', 'options': ['/build',
WithDebInfo'], 'arguments': ['SecondLife.sln']}}]
executing configure command cmake -DCMAKE_BUILD_TYPE:STRING=RelWithDebInfo
D=FALSE ../indra
CMake Error: CMake was unable to find a build program corresponding to
"Visual S
tudio 8 2005".  CMAKE_MAKE_PROGRAM is not set.  You probably need to select
a di
fferent build tool.
CMake Error: Could not find cmake module
CMake Error: Could not find cmake module
-- Configuring incomplete, errors occurred!
default configuration returned 1
Traceback (most recent call last):
  File "D:\Python26\Scripts\autobuild", line 47, in <module>
    sys.exit( Autobuild().main(sys.argv[1:]) )
  File "D:\Python26\lib\site-packages\autobuild\autobuild_main.py", line
188, in
"D:\Python26\lib\site-packages\autobuild\autobuild_tool_configure.py", li
ne 88, in run
    raise ConfigurationError("default configuration returned %d" % (result))
ConfigurationError: default configuration returned 1
ERROR: default configuration returned 1
For more information: try re-running your command with --verbose or --debug


On Wed, Feb 16, 2011 at 3:01 PM, Oz Linden (Scott Lawrence) <
oz at lindenlab.com> wrote:

> Tomorrow and Friday (Feb 17 & 18), Linden Lab is going to be holding an
> in-house Hackathon (stopping work on many other things, getting many
> developers together all at once, and focusing on getting a lot done in short
> time) to upgrade our builds of all our libraries and the viewer to a new
> toolchain, including our new package management tool (autobuild<https://wiki.secondlife.com/wiki/Autobuild>)
> and Visual Studio 2010 for Windows (yes... about time... whatever... we're
> doing it).
> Our goals are simply stated:
>    1. Get all open source components into repositories under
>    hg.secondlife.com (eg bitbucket.org/lindenlab/).  All the third party
>    components (things not created by LL) that we incorporate will be in
>    repositories named with the prefix "3p-".  Most of these repositories exist
>    now, but not all have sources in them yet.
>    2. Get each component packaged with an autobuild configuration for
>    whatever platforms it is needed on.
>    3. Get each component needed on Windows building under autobuild with
>    VS 2010.
>    4. Get a TeamCity-automated build configured for each component
>    repository with the resulting prebuilds of open components uploaded to
>    public directories.
>     5. Get the viewer built using the resulting prebuilt libraries, also
>    under autobuild with VS 2010.
> We also expect to integrate some automated viewer testing into our
> automated viewer builds, but none of that will be externally visible.
> If you make a chart with a row for each component, and a column for each of
> 1 through 4 above, it's a lot of boxes to fill in... many have already been
> done: there are some complete rows, but it's still a big job.
> I will be providing public updates on the wiki (form and location TBD...
> watch this thread) and on the #opensl IRC channel of how we're doing and the
> status of each public repository.
> A non-goal for the Lindens is building the components with Visual Studio
> Express.  There is currently a limitation (see OPEN-1 in jira) that makes
> using Express cumbersome (it requires separate configuration). We do
> recognize that Express is important to open developers, and want it to be
> supported, but there's only so much we can do ourselves in two days.  There
> is an autobuild configuration checked in for building the viewer under
> autobuild including VS Express:
> http://bitbucket.org/oz_linden/viewer-autobuild<http://bitbucket.org/mani_linden/viewer-autobuild>
> I'm going to try to get some supporting documentation up on the wiki today
> or early tomorrow.  It should be possible for open developers to help us
> test whether or not the component builds can be used in Express as we go
> along.  If people want to do that and feed me changes, I'll try to get them
> incorporated in real time as much as possible.
> Once all this is done (and it probably will not be merged to
> viewer-development immediately after the hackathon), this new toolchain will
> be the "supported" way to build the viewer and its dependencies, which means
> that if you really need to build with other tools, you'll have to work out
> how to do so - we'll consider accepting changes to support them so long as
> they're reasonably clean and don't break the standard way of doing it.
> Maintaining support for building with older versions of Visual Studio will
> _not_ be a goal, and getting review time for them will probably be hard.
> _______________________________________________
> Policies and (un)subscribe information available here:
> http://wiki.secondlife.com/wiki/OpenSource-Dev
> Please read the policies before posting to keep unmoderated posting
> privileges

This email is a private and confidential communication. Any use of email may
be subject to the laws and regulations of the United States. You may not
Repost, Distribute nor reproduce any content of this message.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.secondlife.com/pipermail/opensource-dev/attachments/20110218/e83abbf1/attachment.htm 

More information about the opensource-dev mailing list