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.
Gert Driesen
Tasks
0.85
Public
|
Date: 2005-04-02 16:13 Logged In: YES |
|
Date: 2005-04-01 22:36 Logged In: YES |
|
Date: 2005-03-31 15:20 Logged In: YES |
|
Date: 2005-03-30 19:23 Logged In: YES |
| Filename | Description | Download |
|---|---|---|
| NantTest.zip | Download |
| Field | Old Value | Date | By |
|---|---|---|---|
| status_id | Open | 2005-04-02 16:13 | drieseng |
| resolution_id | None | 2005-04-02 16:13 | drieseng |
| category_id | Core | 2005-04-02 16:13 | drieseng |
| assigned_to | nobody | 2005-04-02 16:13 | drieseng |
| close_date | - | 2005-04-02 16:13 | drieseng |
| File Added | 128149: NantTest.zip | 2005-04-01 22:36 | rjontilt |
Copyright © 2010 Geeknet, Inc. All rights reserved. Terms of Use