Hello Gert,
I currently do not have anything that is small that can be sent. Even
my one small project requires one other larger Shared Libraries project
to be already built before it can build and therefore making it hard to
send you anything.
And as I was saying if the Shared Libraries project is not built
properly all other projects that use the Shared Libraries will also not
discard the correct libraries....
One other thing that we are doing is all our products are Multilanguage
and therefore we have created our own MFC/MSVCRT libraries that support
Unicode that will work on all platforms. These libraries also have to
be listed early in the LIB environment path so that ours are found first
before the Microsoft MFC libraries....
Anyways how does the Solution task use the environment paths? Maybe I
am not using the setenv task correctly for INCLUDE and LIB paths! Could
you give me an example of one that shows the correct usage? I have it
actually in to files, one is an included file that loads all the common
paths among projects and then in the individual project .build files I
include the paths that are specific to those projects. I even do a get
of the environment variables after setting them just to see what was
set:
<property name="pathTest"
value="${environment::get-variable('INCLUDE')}" />
<echo message="Checking INCLUDE...: ${pathTest}" level="Info" />
<property name="pathTest"
value="${environment::get-variable('LIB')}" />
<echo message="Checking INCLUDE...: ${pathTest}" level="Info" />
And the output results of this were correct. It showed the Platform SDK
paths first and then the usual standard ones after.
Again are there any other settings that are to be used that may get NAnt
to build the solutions properly or will I end up having to switch to the
exec task and call devenv with the /useenv flag to use the dos
environment variables????
Also what updates have be done to the Nightly build of NAnt since we
last updated, which again was 2005-11-13
Thanks for you help.
Tim Mayert.
-----Original Message-----
From: Gert Driesen [mailto:[EMAIL PROTECTED]
Sent: February 1, 2006 11:58 AM
To: Tim Mayert; nant-users@lists.sourceforge.net
Subject: RE: [NAnt-users] Nant build by solution task not using the
environment paths correctly
Tim,
Can you send me a small repro for this issue ?
Gert
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Tim Mayert
> Sent: woensdag 1 februari 2006 16:25
> To: nant-users@lists.sourceforge.net
> Subject: [NAnt-users] Nant build by solution task not using
> the environment paths correctly
>
> Okay I have an issue that needs solving ASAP.
>
> I am using the solution task to build the entire project
> solution and I
> use the setenv task to set the include and lib folders. This
> seemed to
> work as the projects would all build without any errors about not
> finding the include or lib paths. But since these builds
> were only used
> for testing the build scripts and not actually used in install and
> product testing I did not notice the problem with the built files.
>
> We are now going full production on the Nant builds and therefore when
> the product output of the build was placed into an Install and tested
> we found out that it would not work on 98 machines.
>
> It took us a bit, but we have tracked down the issue to be
> that the Nant
> build, by solution task, does not discard specific libraries
> that are to
> be discarded at the end of the project build.
>
> Here are the libraries that are discarded normally from the build of a
> project when built by Studio .NET 2003: LINK : warning LNK4089: all
> references to 'OLEAUT32.dll' discarded by /OPT:REF
> LINK : warning LNK4089: all references to 'SHELL32.dll' discarded by
> /OPT:REF
> LINK : warning LNK4089: all references to 'imagehlp.dll' discarded by
> /OPT:REF
> LINK : warning LNK4089: all references to 'ole32.dll' discarded by
> /OPT:REF
>
> But when built by Nant the only library that is discarded is: LINK :
> warning LNK4089: all references to 'OLEAUT32.dll' discarded by
> /OPT:REF
>
> So we looked into this a little more and noticed that if we place the
> Microsoft Platform SDK include and lib paths further down in the list
> of paths to set then even Studio would also only discard that
> first library
> one. So as long as the Platform SDK was declared at the beginning of
> the LIB and INCLUDE paths the Studio would build the app properly and
> discard the correct libraries.
>
> So I made sure using the setenv task, in NAnt, that I declared the
> Platform SDK paths to be first in the list. After setting this I
> rebuilt and notice that this did not affect the build at all. It
> still only discarded the one dll library.
>
> I still do not know if the solution task uses the environment
> variables
> correctly or is it still not using the solution/project configurations
> correctly.
> Has anyone had issues with the solution task not building the
> same as if
> you build through the Studio IDE?
>
> Now I did not want to complicate my build by having to run
> cl, link, ...
> Etc tasks separately as we should not have to if the solution task
> worked properly.
>
> Anyhow is there anything that I could do to fix this issue? Is there
> maybe a newer build of Nant that may handle solution tasks/environment
> variables better? We are currently using the nightly build from:
> nant-0.85-nightly-2005-11-13
>
> Any help would be appreciated.....
>
> Thanks,
>
> Tim Mayert.
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep
> through log files
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web.
> DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=k&kid3432&bid#0486&dat1642
> _______________________________________________
> NAnt-users mailing list
> NAnt-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nant-users
>
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_______________________________________________
NAnt-users mailing list
NAnt-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users
