Re: Can't get vcbuild to build a project with dependant projects

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

jeanne.petrangelo@xxxxxxxxx wrote:
Ajay Kalra wrote:
<jeanne.petrangelo@xxxxxxxxx> wrote in message
news:1156432350.303062.102250@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Does anyone else have this problem, and is there a workaround? Am I
missing something?

I am converting a VC6 workspace to a VC2005 solution, and using an
nmake makefile for automated builds. It consists of numerous projects
which are mostly independant and built separately. There is one project
(A) that depends on three other projects (B, C, and D). From the
command line, I can use vcbuild to build B, C, and D, but when I try to
build A I get a slew of link errors. Within the IDE, I have no problems
building A.

I've made sure the IDE has explicit dependency assignments between the
projects. I've also tried using the IDE to add project property linker
depencencies on specific dependant libraries, explicitly, but I may be
missing something.

I encountered the same problem when I set up the projects. The order was all
fine when I built within IDE but it was all broken when I did the build on
command line. IDE is smart enough to figure out the build order based on
library that a project links with. In addition, you have to explicitly set
the order in the solution. Open the solution and right click on it. In the
context menu, you will see the Build Order. You need to set it here and then
try it again on command line. This is for the non-express edition. I suspect
the VCE will have the same feature.

Thank you Ajay! This does clear some things up for me. I'm new to the
whole world of Visual Studio. I have seen the build order in VCE, and I
think I need to make sure the linker settings are correct for each
individual project.

This application is a console app that talks to the embedded device
we're programming using a cross-compiler, over USB. Many of the VC
projects have interactive commands that are specific to certain parts
of our code, which may or may not be used on a given project, so they
may or may not be maintained at a given moment. That's why I can't just
build the whole solution; any unmaintained project could break the
build. I'm normally one who is writing C code for the embedded target
and not worrying about how this console app works.

I believe, in the IDE, I need to open Project Properties, and under
Linker, there are three things I need to pay attention to. Under
"Advanced" I can set the "import library" which is the library created
by this project. That was a bit confusing to me because I associate the
word "import" with something that is taken in, not created. Under
"Input" there is a place for "Additional Dependencies" and this is
where I make sure each project knows about the libraries created by
other projects. I don't use any paths here. Under "General" there is
"Additional Library Directories" and this is where I put the paths to
the library files needed by this project (the ones I set in Additional
Dependencies).

If I'm missing anything, or didn't get that right, please let me know!

I really don't know why msdev would be able to sort all this out and
msbuild can't, but I'll give it the old college try.

It turns out once I set all the linkage and dependencies correctly,
vcbuild could handle it just fine; I don't need msbuild, although that
worked fine too. Is there any reason I should choose one over the
other?

Here's a link to an MSDN forum where I had originally asked for help,
and where I explicitly spelled out the steps to take to address the
problem, for other newbies like me:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=668910&SiteID=1&mode=1

Thanks again,
Jeanne

.

Relevant Pages

  • Re: Cant get vcbuild to build a project with dependant projects
    ... missing something? ... command line, I can use vcbuild to build B, C, and D, but when I try to ... I've made sure the IDE has explicit dependency assignments between the ... depencencies on specific dependant libraries, explicitly, but I may be ...
    (microsoft.public.vc.language)
  • Re: Delphi 8 vs Visual Studio
    ... editing support is missing, but also the libraries themselves are ... It's also very easy to tweak the VS IDE: ...
    (borland.public.delphi.non-technical)
  • Re: Delphi 8 vs Visual Studio
    ... > editing support is missing, but also the libraries themselves are ... so all you're buying is an IDE). ... > It's also very easy to tweak the VS IDE: ...
    (borland.public.delphi.non-technical)
  • Re: Ann: Luxasm 00.01.00 (2004-04-08)
    ... >> itself before the IDE is handled, ideally by someone else as I am ... > The only thing I've got against Motif is I don't know anything about it. ... (You will need the GNU lesstif libraries to run them.) ... due to the way the LGPL works, ...
    (alt.lang.asm)
  • Re: tech:Skins game boot process
    ... damn thing still wont boot up, ... The IDE connector pin missing on the IDE board ...
    (rec.games.video.arcade.collecting)