help with dev environment?

I’m looking to build some generic code and link it with some OS specific
code, and I’d like to seperate the 2 into 2 different directories. The
IFS build environment doesn’t seem to like it if i use a …\gen<blah>.c
in my sources.inc file, so i placed a makefile\sources\sources.inc in
each of my os and gen dirs, and then compile all the gen code into a
library and link the osd code against this. Is there a better way to do
this? Will this cause any problems with a kernel driver?

Thanks,
Allan

Build a LIB from one directory and link it to the build of another one.

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

----- Original Message -----
From: “Allan Graves”
To: “Windows File Systems Devs Interest List”
Sent: Saturday, October 22, 2005 2:40 AM
Subject: [ntfsd] help with dev environment?

> I’m looking to build some generic code and link it with some OS specific
> code, and I’d like to seperate the 2 into 2 different directories. The
> IFS build environment doesn’t seem to like it if i use a …\gen<blah>.c
> in my sources.inc file, so i placed a makefile\sources\sources.inc in
> each of my os and gen dirs, and then compile all the gen code into a
> library and link the osd code against this. Is there a better way to do
> this? Will this cause any problems with a kernel driver?
>
> Thanks,
> Allan
>
> —
> Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17
>
> You are currently subscribed to ntfsd as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com

BUILD/SOURCES will only do one level of directory structure. Thus you can
say “…\what.c” but BUILD will not use “…\BLAH\what.c”. At least I have
never gotten more than "…" to work. Nor can you have a DIRS and a SOURCES
file co-existent in the same directory. Like Max said… build libraries and
link them in a final link.


The personal opinion of
Gary G. Little

“Allan Graves” wrote in message
news:xxxxx@ntfsd…
> I’m looking to build some generic code and link it with some OS specific
> code, and I’d like to seperate the 2 into 2 different directories. The
> IFS build environment doesn’t seem to like it if i use a …\gen<blah>.c
> in my sources.inc file, so i placed a makefile\sources\sources.inc in each
> of my os and gen dirs, and then compile all the gen code into a library
> and link the osd code against this. Is there a better way to do this?
> Will this cause any problems with a kernel driver?
>
> Thanks,
> Allan
>