Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Project Configurations are out of date -- another solution for Libraries/LIB files

102 views
Skip to first unread message

Charles Cafrelli

unread,
May 26, 2003, 9:37:44 PM5/26/03
to
After upgrading VS .NET 2003 from Visual Studio .NET 2002, several of
my projects went into eternal rebuild mode. I had several libraries
modules that would continuously be reuilt. I could hit the Build
Solution button 5 times in a row and EVERY TIME I'd get "Creating
Library...". Then when I hit the Play button, I'd get "Project
Configurations are out of date" Would you like to Rebuild?

I JUST REBUILT EVERYTHING 5 TIMES!!!!!

I changed every project dependency around and went through every
permutations of build order I could think of. (Side note: What a
"brilliant" form for determining project build order. No, I can't
click and drag the projects to sort my order listing, like every other
list box in the known universe, I have to check mark the dependendant
libs in ANOTHER window and go through the WHOLE FRIGGIN BUILD TREE to
properly setup my build dependencies, THEN jump back to the project
build order window to see if it did what I want! Do you realize it
was 100 times faster and easier for me just to text edit the SLN file
and cut and paste the build order than it was to use the GUI!?!?)

>whew< Okay, back off the soap box...

The existing errors I could google for didn't help my problem and
neither did the Knowledgebase RC fix. This is specific to LIB or
Library files.

Here's the fix for this one (Somebody at MS owes me about 10 hours of
walking through dependencies, perusing vcproj files and countless
hours spent rebuilding for no reason whatsoever... or maybe a
T-shirt... :) )

In the Project property page, under Librarian | General you'll see an
entry for Output File. Previously, back slashes and forward slashes
were treated identically. (IE /mylibs/bin/Strings.Lib =
\mylibs\bin\Strings.lib )

Not anymore. Even though the compiler will recognize the forward
slashes, build the lib and put it in the right directory, the
DEPENDENCY CHECKER WILL NOT. The dependency checker wants backslashes
only and if that's what you have, it's rebuild time for you. So if
you've got forward slashes, convert 'em.

And now you know... the rest of the story.

0 new messages