Visual Studio library path size limit

I have a project which takes quite a lot of library paths, due to our
environment setup. The problem now is that the line in the *.dsp filefor the
linker is more than 4Kb long. Is there a limit on how long the line may be?

I mean the
# ADD LINKER32 <linkeroptions>
in the dsp file.

When I paste in the project file all the library paths then Visual Studio can
compile it, but when I exit the project VC asks me to safe the changes to the
project file and when I try to reload the project the line is crippled.

Any ideas how to circumvent this size limit?

I tried to spread the line over several lines which worked, but as soon as I
change something in the settings Visual Studio will rewrite the dsp file and
create the long line again.

--
Gerhard Gruber

Für jedes menschliche Problem gibt es immer eine einfache Lösung:
Klar, einleuchtend und falsch. (Henry Louis Mencken)

Maxim
Mon Oct 20 13:36:09 CDT 2003

Get rid of VC++'s project management/building and use MAKEFILE/SOURCES
instead.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com


"Gerhard W. Gruber" <sparhawk@gmx.at> wrote in message
news:0598pvohe0tinumupb75m4uck475bbcf2q@4ax.com...
> I have a project which takes quite a lot of library paths, due to our
> environment setup. The problem now is that the line in the *.dsp filefor the
> linker is more than 4Kb long. Is there a limit on how long the line may be?
>
> I mean the
> # ADD LINKER32 <linkeroptions>
> in the dsp file.
>
> When I paste in the project file all the library paths then Visual Studio can
> compile it, but when I exit the project VC asks me to safe the changes to the
> project file and when I try to reload the project the line is crippled.
>
> Any ideas how to circumvent this size limit?
>
> I tried to spread the line over several lines which worked, but as soon as I
> change something in the settings Visual Studio will rewrite the dsp file and
> create the long line again.
>
> --
> Gerhard Gruber
>
> Für jedes menschliche Problem gibt es immer eine einfache Lösung:
> Klar, einleuchtend und falsch. (Henry Louis Mencken)

Gerhard
Mon Oct 20 16:03:52 CDT 2003

On Mon, 20 Oct 2003 22:36:09 +0400 wrote "Maxim S. Shatskih"
<maxim@storagecraft.com> in microsoft.public.development.device.drivers with
<#UlpHkzlDHA.2436@TK2MSFTNGP09.phx.gbl>

> Get rid of VC++'s project management/building and use MAKEFILE/SOURCES
>instead.

We have makefiles, but I wrote a script to convert our makefiles to visual
studio files. I wanted to sue this because the classbrowser helps a lot, so I
wouldn't miss that feature.

--
Gerhard Gruber

Für jedes menschliche Problem gibt es immer eine einfache Lösung:
Klar, einleuchtend und falsch. (Henry Louis Mencken)

Jeff
Tue Oct 21 07:00:54 CDT 2003

"Gerhard W. Gruber" <sparhawk@gmx.at> wrote in message
news:ccj8pvsiaso3ijhs82b116qs127n568klr@4ax.com...
> On Mon, 20 Oct 2003 22:36:09 +0400 wrote "Maxim S. Shatskih"
> <maxim@storagecraft.com> in microsoft.public.development.device.drivers
with
> <#UlpHkzlDHA.2436@TK2MSFTNGP09.phx.gbl>
>
> > Get rid of VC++'s project management/building and use
MAKEFILE/SOURCES
> >instead.
>
> We have makefiles, but I wrote a script to convert our makefiles to visual
> studio files. I wanted to sue this because the classbrowser helps a lot,
so I
> wouldn't miss that feature.

You can use external makefiles with Visual Studio without losing the class
browser. DDKBuild.bat
(http://www.hollistech.com/Resources/ddkbuild/ddkbuild.htm) was written
exactly for this purpose -- I (and many other DDK developers) use it every
day.

Maxim
Tue Oct 21 07:32:18 CDT 2003

> > Get rid of VC++'s project management/building and use MAKEFILE/SOURCES
> >instead.
>
> We have makefiles, but I wrote a script to convert our makefiles to visual
> studio files. I wanted to sue this because the classbrowser helps a lot, so I
> wouldn't miss that feature.

Class browser is available by adding some keyword to SOURCES file.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com

Jeff
Tue Oct 21 13:36:31 CDT 2003

"Maxim S. Shatskih" <maxim@storagecraft.com> wrote in message
news:%23PAcxK%23lDHA.3732@tk2msftngp13.phx.gbl...
> > > Get rid of VC++'s project management/building and use
MAKEFILE/SOURCES
> > >instead.
> >
> > We have makefiles, but I wrote a script to convert our makefiles to
visual
> > studio files. I wanted to sue this because the classbrowser helps a lot,
so I
> > wouldn't miss that feature.
>
> Class browser is available by adding some keyword to SOURCES file.

BROWSER_INFO=1
BROWSERFILE=$(TARGETNAME).bsc -n

as noted in the doc page for DDKBUILD.

David
Tue Oct 21 14:28:52 CDT 2003

I like the following:
BROWSER_INFO=1
BSCMAKE_FLAGS=-n -v


You might have to find a BSCMAKE program from the Visual Studio directory
and put it in the DDK\bin directory if you are using the DDK that didn't
include it. I use CodeWright to view the browse file.



"Jeff Henkels" <jeff@mapson.privatemail.com> wrote in message
news:OHK6BJAmDHA.1408@TK2MSFTNGP11.phx.gbl...
> "Maxim S. Shatskih" <maxim@storagecraft.com> wrote in message
> news:%23PAcxK%23lDHA.3732@tk2msftngp13.phx.gbl...
> > > > Get rid of VC++'s project management/building and use
> MAKEFILE/SOURCES
> > > >instead.
> > >
> > > We have makefiles, but I wrote a script to convert our makefiles to
> visual
> > > studio files. I wanted to sue this because the classbrowser helps a
lot,
> so I
> > > wouldn't miss that feature.
> >
> > Class browser is available by adding some keyword to SOURCES file.
>
> BROWSER_INFO=1
> BROWSERFILE=$(TARGETNAME).bsc -n
>
> as noted in the doc page for DDKBUILD.
>
>