Build sources annoyance

Hi all,
I am trying to reference a source file two directories back from
where I’m calling build, and I get the following error from build:

Ignoring invalid directory prefix in SOURCES= entry: …..\irpnames.c

Anyone know why this would be? The weird thing is that …\something.c works
just fine…

Thanks,
Matt

It is the way it is. You can go up one (I think) or down one. So side
or anywhere else.

“Matthew N. White” wrote in message
news:xxxxx@ntdev…
> Hi all,
> I am trying to reference a source file two directories back from
> where I’m calling build, and I get the following error from build:
>
> Ignoring invalid directory prefix in SOURCES= entry: …..\irpnames.c
>
> Anyone know why this would be? The weird thing is that …\something.c
works
> just fine…
>
> Thanks,
> Matt
>
>
>

Welcome to the wonderful world of BUILD. It can only deal with
source code in the same or parent directory of the “sources” file.
It cannot use source files from arbitrary locations.

A possible kludge is to create a stub in the current directory that
just contains one line: #include “…..\filename.c”. A much better
solution is to restructure your directory layout. If you have some
code that needs to be shared between directories, compile it into
a static library. The “BUILD way” is to share object code via static
libraries, not to share source files.

-----Original Message-----
From: Matthew N. White
Sent: Monday, April 12, 2004 10:54 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Build sources annoyance

Hi all,
I am trying to reference a source file two directories back from
where I’m calling build, and I get the following error from build:

Ignoring invalid directory prefix in SOURCES= entry: …..\irpnames.c

Anyone know why this would be? The weird thing is that …\something.c
works
just fine…

Thanks,
Matt

Wow. Thanks guys. This makes my day :wink:

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of McNamee, John
Sent: Monday, April 12, 2004 12:58 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Build sources annoyance

Welcome to the wonderful world of BUILD. It can only deal with source code
in the same or parent directory of the “sources” file.
It cannot use source files from arbitrary locations.

A possible kludge is to create a stub in the current directory that just
contains one line: #include “…..\filename.c”. A much better solution is
to restructure your directory layout. If you have some code that needs to
be shared between directories, compile it into a static library. The “BUILD
way” is to share object code via static libraries, not to share source
files.

-----Original Message-----
From: Matthew N. White
Sent: Monday, April 12, 2004 10:54 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Build sources annoyance

Hi all,
I am trying to reference a source file two directories back from
where I’m calling build, and I get the following error from build:

Ignoring invalid directory prefix in SOURCES= entry: …..\irpnames.c

Anyone know why this would be? The weird thing is that …\something.c works
just fine…

Thanks,
Matt


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@bitarmor.com To unsubscribe
send a blank email to xxxxx@lists.osr.com