Marcus Rohrmoser wrote:
> Korenkiewicz, Mark schrieb:
> > Marcus,
> > When it comes to MS Visual Studio there are things like version numbers
> > built into compiled DLLs, VS project files that have build options and
> > stuff, all of which may be critical to building a specific version of an
> > EXE or DLL. In many cases, all this stuff needs to be under SCM.
> I think you should NEVER use a IDE as a build tool (as you wouldn't vice
> versa ;-)). I used nant to build my VS projects based on a fresh
> svn co of the desired version (tag).
Does this work from .vcproj/.sln files as 'primary' source or do you
have to manually synchronize a second build system (nant in this case)?
I am asking because I am currently trying to get an idea how multi-
platform automated builds may work out. My latest idea is to ssh to
these machines, run svn export, call the 'native' build system, and
check in the results into a secondary repository. Biggest obstacle
so far is to get VS7 batch job reliably build the things I want it
to build. I'd be happy if there was a solution that does not
involve the IDE yet runs directly on a .vcproj or .sln file as this
is the thing the developers actively maintain.
To get back on the SVN track:
> Still: Never saw a occasion where compiler output versioning made sense.
It's sometimes hard to maintain 'intermediate build data' like
shared libraries, that are used (yet not easily built) by other in-house
in an orderly fashion.
So far most places I know use the 'traditional' approach (dump all stuff
in a silent corner on some NFS server and hope that people find out
what's there and why) recommended but I suppose that's a place where
putting this stuff into a repository might make sense.
I am not sure, though.
> > Is there some limitation in Subversion that prevents this?
> > Mark Korenkiewicz
> > ITSC/Mitretek Systems
> > College Park, MD
> >>-----Original Message-----
> >>From: Marcus Rohrmoser [mailto:firstname.lastname@example.org]
> >>Sent: Monday, March 21, 2005 7:41 AM
> >>To: email@example.com
> >>Subject: Re: Where is binary files should be placed?
> >>I think only things hard to create (e.g. source code that is
> >>manually edited) should go into version control. Everything
> >>else (compile/build output, generated docs etc.) shouldn't be
> >>in the repository at all.
> >>Hope this helps,
> >> M
> >>oleksa borodie schrieb:
> >>> Help me please I'm new with subversion. Where is binary
> >>files should
> >>>be placed? I mean where is build output directory should
> >>be? Is there
> >>>any common practice? I'm using MS Visual Studio.
> >>> I could place it inside project directory project1/bin
> >>>and ignore with global-ignores option inside configuration file. On
> >>>the each developer computer this file should be edited -
> >>someone could
> >>>forget edit it.
> >>> I could move it out of the project folder output/project1/
> >>>but what if I will need add some files from bin folder?
> >>> Could you give me advice please?
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Mar 22 13:20:34 2005