How do I build all projects on the trunk?

1 view
Skip to first unread message

Jason Meckley

unread,
Oct 24, 2008, 11:05:28 AM10/24/08
to Castle Project Users
I downloaded the trunk this morning to build with the latest NH trunk
(which will make it's way into Rhino.Tools).

I have the build running successfully with tests. (required a previous
version of AllComponentsReleasePolicy.cs to be 2.0 compatible.) So
it's successful in building part of the stack but not the entire
stack. It's not building
AR, Facilities or MR.

I modified the release.cmd to this
@echo off
"C:\Program Files\nant\nant-0.86-nightly-2008-08-18\bin\nant" -
t:net-2.0 -f:release.build package-net-2.0 %*
"C:\Program Files\nant\nant-0.86-nightly-2008-08-18\bin\nant" rebuild

it runs without error, to the best of my knowledge, but the debug and
release build directories only contain assemblies for:
Core
DynamicProxy
DynamicProxy2
Services.Logging
Services.Transaction
other 3rd party assemblies.

How can I adjust by command above to also build ActiveRecord,
Facilities and the associated tests? MR isn't required at this point.

Ayende Rahien

unread,
Oct 24, 2008, 1:16:40 PM10/24/08
to Castle Project Users
Are you running build-from-trunk?

Jason Meckley

unread,
Oct 24, 2008, 1:33:54 PM10/24/08
to Castle Project Users
no I don't think so. I don't see any files castle that say build-from-
trunk. if you're talking rhino, then no I'm not there yet.
I output the log to a text file. come to find out the projects are not
compiling correctly, seems to be a 3.0 > syntax errors. I'm updating
nant to target 3.5 instead of 2.0.

Off topic a little bit, but 3.5 compilation for 2.0 is confusing with
nant. If the code uses a 3.0 > feature and is compiled using 3.5
framework can I then use that assembly in a 2.0 project? For example,
NH required the 3.5 framework to compile, but runs on 2.0. Why use 3.5
if you're targeting 2.0? is the same true for castle?

Ok, just found out:
"C:\Program Files\nant\nant-0.86-nightly-2008-08-18\bin\nant" -
t:net-3.5 -f:release.build package-net-2.0 %* >ouptput-release-
build.log
doesn't compile with errors about var being undefined. I know that
one.

Jason Meckley

unread,
Oct 24, 2008, 1:53:05 PM10/24/08
to Castle Project Users
looking into Rhino BuildFromTrunk.build I need to update SVN, so I'm
updating to 1.5.4. I'll get there eventually:)

Ayende Rahien

unread,
Oct 24, 2008, 1:58:02 PM10/24/08
to castle-pro...@googlegroups.com
The way I work when I want to do this is by:
compiling castle
copy castle.core, castle.dynamicproxy2 to nh's sharedlibs
compiling nhibernate
compiling the nhibernate dlls to castle shared libs
compiling castle 
compiling castle libs to rhino shared libs
compile rhino

Jason Meckley

unread,
Oct 24, 2008, 2:34:57 PM10/24/08
to Castle Project Users
ok, I'll change my order up. I was doing:
NH
Castle
Rhino

Jason Meckley

unread,
Oct 24, 2008, 4:12:57 PM10/24/08
to Castle Project Users
finally got this working. there where some syntax downgrades required
in InversionOfControl to compile with 2.0.
I also needed to update AR Facility to implement ISession from NH
trunk.

if others want i can supply a patch.

On Oct 24, 2:34 pm, Jason Meckley <jasonmeck...@gmail.com> wrote:
> ok, I'll change my order up. I was doing:
> NH
> Castle
> Rhino
>
> Ayende Rahien wrote:
> > The way I work when I want to do this is by:compiling castle
> > copy castle.core, castle.dynamicproxy2 to nh's sharedlibs
> > compiling nhibernate
> > compiling the nhibernate dlls to castle shared libs
> > compiling castle
> > compiling castle libs to rhino shared libs
> > compile rhino
>

Ayende Rahien

unread,
Oct 24, 2008, 4:58:31 PM10/24/08
to castle-pro...@googlegroups.com
Please do
Reply all
Reply to author
Forward
0 new messages