lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Currens <currens.ch...@gmail.com>
Subject Re: build scripts
Date Mon, 23 Jul 2012 21:23:11 GMT
Yeah.  In Visual Studio you can just change the release configuration
manually, and no matter what, it will only build for the framework you have
selected.  With the build script, I didn't know how to update jenkins and I
knew that in all deploy cases we needed both built, so for the time being
it does it automatically...this will change in the future, though we do
still need to build both in the CI server, and also need to build both
whenever we make a nuget package.  I'm trying to think of a maintainable
way to have the packaging system make sure both of the framework targets
have been run before building the nuget package.  That would probably be
the most challenging part of it, which is probably not that challenging at
all. ;)

Thanks,
Christopher


On Mon, Jul 23, 2012 at 2:18 PM, Michael Herndon <
mherndon@wickedsoftware.net> wrote:

> heh, I thought the peculiar thing was that it was just building the .NET
> 3.5 version randomly instead of being an actual deliberate change.  I was
> trying to think how that was possible. =)
>
>
> On Sun, Jul 22, 2012 at 2:55 PM, Christopher Currens <
> currens.chris@gmail.com> wrote:
>
> > It is, but I didn't want to deal with changing our CI server
> configuration
> > to get what is a little bit of benefit (at the moment) for the amount of
> > time it would have taken me to figure it all out.  At the moment, the
> kind
> > of packaging we need for a release would be both frameworks, so as of
> now,
> > I have it outputting both.  I am not oblivious to the awkwardness of the
> > build scripts how they are now, as the most glaringly obvious flaw with
> > outputting both, is that nunit runs the tests for .NET35 and .NET4 at the
> > same time. There are several things wrong with the way that works.
> >
> > It's not a hefty change, though, that needs to be done if you wanted to
> > change it to a build parameter, I have a mostly finished patch for that
> > since that was original first goal.  There's an extra build step that can
> > be removed and a variable added to each project page.  The larger(?)
> change
> > would the actual packaging for NUnit.  Even though it's already it's own
> > separate target, I'm sure we want to validate that both .NET35 and .NET4
> > builds have been run before packaging the output.
> >
> >
> > Thanks,
> > Christopher
> >
> >
> > On Sun, Jul 22, 2012 at 11:27 AM, Michael Herndon <
> > mherndon@wickedsoftware.net> wrote:
> >
> > > that is a peculiar behavior.
> > >
> > > On Sun, Jul 22, 2012 at 4:41 AM, Christopher Currens <
> > > currens.chris@gmail.com> wrote:
> > >
> > > > Right now, it outputs both automatically.  I didn't put in a switch,
> it
> > > > just does it be default.
> > > >
> > > >
> > > > On Sat, Jul 21, 2012 at 2:38 PM, Michael Herndon <
> > > > mherndon@wickedsoftware.net> wrote:
> > > >
> > > > > you would need create a build variable for the .net framework
> version
> > > > > parameter for msbuild and have it run a second build and switch out
> > the
> > > > > version.
> > > > >
> > > > > On Sat, Jul 21, 2012 at 3:08 PM, Prescott Nasser <
> > > geobmx540@hotmail.com
> > > > > >wrote:
> > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > There was a commit for updating the build scripts - is there
a
> > > command
> > > > I
> > > > > > can run to output both 4.0 and 3.5 binaries of everything?
> > > > > >
> > > > >
> > > >
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message