[nant-dev] [ nant-Bugs-1173529 ] Implied dependancies not considered in solution

2005-04-02 Thread SourceForge.net
Bugs item #1173529, was opened at 2005-03-30 10:44
Message generated for change (Comment added) made by rjontilt
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=1173529group_id=31650

Category: Core
Group: 0.85
Status: Open
Resolution: None
Priority: 5
Submitted By: Ray Johnson (rjontilt)
Assigned to: Nobody/Anonymous (nobody)
Summary: Implied dependancies not considered in solution

Initial Comment:

I have a solution with several C++ projects.  One builds 
a .lib that gets used by the other.  The library project 
has a setting in Linker-Dependencies-Additional 
Dependencies of a system library (NetAPI32.lib).

The other project (that builds an .exe) does not include 
NetAPI32.lib in it's Additional Dependancies section.  
Under VS.Net this does not appear to be a problem.  
Apparently, VS.Net will look at the Additional 
Dependancies of any library projects and include them 
when linking the exe project.

Nant doesn't appear to do this.  The work around is to 
include the needed libraries in the Additional 
Dependancies section of the exe project.  Unfortunantly, 
this is turning out to be rather a pain to maintain.  So 
this bug is to have Nant mimick the behavior of VS.Net 
to include the implied additional dependancies whe 
linking the main executable.

--

Comment By: Ray Johnson (rjontilt)
Date: 2005-04-01 14:36

Message:
Logged In: YES 
user_id=1246077

Ok - I've attached a simple example that reproduces the 
problem.

--

Comment By: Henry (henryl)
Date: 2005-03-31 07:20

Message:
Logged In: YES 
user_id=1083163

This is the same issue as in bug 1124296.

--

Comment By: Gert Driesen (drieseng)
Date: 2005-03-30 11:23

Message:
Logged In: YES 
user_id=707851

Ray, please attach a small repro for this bug report too.

Thanks !

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=1173529group_id=31650


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


[nant-dev] [ nant-Bugs-1173529 ] Implied dependancies not considered in solution

2005-04-02 Thread SourceForge.net
Bugs item #1173529, was opened at 2005-03-30 20:44
Message generated for change (Comment added) made by drieseng
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=1173529group_id=31650

Category: Tasks
Group: 0.85
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Ray Johnson (rjontilt)
Assigned to: Gert Driesen (drieseng)
Summary: Implied dependancies not considered in solution

Initial Comment:

I have a solution with several C++ projects.  One builds 
a .lib that gets used by the other.  The library project 
has a setting in Linker-Dependencies-Additional 
Dependencies of a system library (NetAPI32.lib).

The other project (that builds an .exe) does not include 
NetAPI32.lib in it's Additional Dependancies section.  
Under VS.Net this does not appear to be a problem.  
Apparently, VS.Net will look at the Additional 
Dependancies of any library projects and include them 
when linking the exe project.

Nant doesn't appear to do this.  The work around is to 
include the needed libraries in the Additional 
Dependancies section of the exe project.  Unfortunantly, 
this is turning out to be rather a pain to maintain.  So 
this bug is to have Nant mimick the behavior of VS.Net 
to include the implied additional dependancies whe 
linking the main executable.

--

Comment By: Gert Driesen (drieseng)
Date: 2005-04-02 18:13

Message:
Logged In: YES 
user_id=707851

This is now fixed in cvs. The problem was that we were 
ignoring the additional dependies setting for the lib project.

--

Comment By: Ray Johnson (rjontilt)
Date: 2005-04-02 00:36

Message:
Logged In: YES 
user_id=1246077

Ok - I've attached a simple example that reproduces the 
problem.

--

Comment By: Henry (henryl)
Date: 2005-03-31 17:20

Message:
Logged In: YES 
user_id=1083163

This is the same issue as in bug 1124296.

--

Comment By: Gert Driesen (drieseng)
Date: 2005-03-30 21:23

Message:
Logged In: YES 
user_id=707851

Ray, please attach a small repro for this bug report too.

Thanks !

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=1173529group_id=31650


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


[nant-dev] [ nant-Bugs-1173529 ] Implied dependancies not considered in solution

2005-03-31 Thread SourceForge.net
Bugs item #1173529, was opened at 2005-03-30 10:44
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=1173529group_id=31650

Category: Core
Group: 0.85
Status: Open
Resolution: None
Priority: 5
Submitted By: Ray Johnson (rjontilt)
Assigned to: Nobody/Anonymous (nobody)
Summary: Implied dependancies not considered in solution

Initial Comment:

I have a solution with several C++ projects.  One builds 
a .lib that gets used by the other.  The library project 
has a setting in Linker-Dependencies-Additional 
Dependencies of a system library (NetAPI32.lib).

The other project (that builds an .exe) does not include 
NetAPI32.lib in it's Additional Dependancies section.  
Under VS.Net this does not appear to be a problem.  
Apparently, VS.Net will look at the Additional 
Dependancies of any library projects and include them 
when linking the exe project.

Nant doesn't appear to do this.  The work around is to 
include the needed libraries in the Additional 
Dependancies section of the exe project.  Unfortunantly, 
this is turning out to be rather a pain to maintain.  So 
this bug is to have Nant mimick the behavior of VS.Net 
to include the implied additional dependancies whe 
linking the main executable.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=1173529group_id=31650


---
This SF.net email is sponsored by Demarc:
A global provider of Threat Management Solutions.
Download our HomeAdmin security software for free today!
http://www.demarc.com/Info/Sentarus/hamr30
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


[nant-dev] [ nant-Bugs-1173529 ] Implied dependancies not considered in solution

2005-03-31 Thread SourceForge.net
Bugs item #1173529, was opened at 2005-03-31 02:44
Message generated for change (Comment added) made by henryl
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=1173529group_id=31650

Category: Core
Group: 0.85
Status: Open
Resolution: None
Priority: 5
Submitted By: Ray Johnson (rjontilt)
Assigned to: Nobody/Anonymous (nobody)
Summary: Implied dependancies not considered in solution

Initial Comment:

I have a solution with several C++ projects.  One builds 
a .lib that gets used by the other.  The library project 
has a setting in Linker-Dependencies-Additional 
Dependencies of a system library (NetAPI32.lib).

The other project (that builds an .exe) does not include 
NetAPI32.lib in it's Additional Dependancies section.  
Under VS.Net this does not appear to be a problem.  
Apparently, VS.Net will look at the Additional 
Dependancies of any library projects and include them 
when linking the exe project.

Nant doesn't appear to do this.  The work around is to 
include the needed libraries in the Additional 
Dependancies section of the exe project.  Unfortunantly, 
this is turning out to be rather a pain to maintain.  So 
this bug is to have Nant mimick the behavior of VS.Net 
to include the implied additional dependancies whe 
linking the main executable.

--

Comment By: Henry (henryl)
Date: 2005-03-31 23:20

Message:
Logged In: YES 
user_id=1083163

This is the same issue as in bug 1124296.

--

Comment By: Gert Driesen (drieseng)
Date: 2005-03-31 03:23

Message:
Logged In: YES 
user_id=707851

Ray, please attach a small repro for this bug report too.

Thanks !

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=1173529group_id=31650


---
This SF.net email is sponsored by Demarc:
A global provider of Threat Management Solutions.
Download our HomeAdmin security software for free today!
http://www.demarc.com/Info/Sentarus/hamr30
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


[nant-dev] [ nant-Bugs-1173529 ] Implied dependancies not considered in solution

2005-03-30 Thread SourceForge.net
Bugs item #1173529, was opened at 2005-03-30 20:44
Message generated for change (Comment added) made by drieseng
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=1173529group_id=31650

Category: Core
Group: 0.85
Status: Open
Resolution: None
Priority: 5
Submitted By: Ray Johnson (rjontilt)
Assigned to: Nobody/Anonymous (nobody)
Summary: Implied dependancies not considered in solution

Initial Comment:

I have a solution with several C++ projects.  One builds 
a .lib that gets used by the other.  The library project 
has a setting in Linker-Dependencies-Additional 
Dependencies of a system library (NetAPI32.lib).

The other project (that builds an .exe) does not include 
NetAPI32.lib in it's Additional Dependancies section.  
Under VS.Net this does not appear to be a problem.  
Apparently, VS.Net will look at the Additional 
Dependancies of any library projects and include them 
when linking the exe project.

Nant doesn't appear to do this.  The work around is to 
include the needed libraries in the Additional 
Dependancies section of the exe project.  Unfortunantly, 
this is turning out to be rather a pain to maintain.  So 
this bug is to have Nant mimick the behavior of VS.Net 
to include the implied additional dependancies whe 
linking the main executable.

--

Comment By: Gert Driesen (drieseng)
Date: 2005-03-30 21:23

Message:
Logged In: YES 
user_id=707851

Ray, please attach a small repro for this bug report too.

Thanks !

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=1173529group_id=31650


---
This SF.net email is sponsored by Demarc:
A global provider of Threat Management Solutions.
Download our HomeAdmin security software for free today!
http://www.demarc.com/Info/Sentarus/hamr30
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers