In a misguided fit of brazen self delusion I attempted to build a little bit
of UI in a driver project using WTL. MAKFILE.NEW has long had what seems
like good plumbing to bring WTL & ATL into a usermode build target. The
only thing that is missing is about half of the API header files that WTL is
expecting to find J
So anybody have any guidance on how to mix back in the Platform SDK header
files that seem to be forever pruned from the WDK?
I did drop the whole notion and went back to just coding Window / Dialog Box
/ Property Page UI in the style of the Bronze Age.
I just am wondering if anyone would like to share a satisfactory solution or
share gentle (or violent!) opposition to the whole idea.
Thanks,
Dave Cattley
Ah… there once was a time when the WDK included “everything you need” to build drivers and the control panel craplets they required. Even applications!
Sadly, those days are behind us. It’s too bad, cuz I think “build” is a pretty good tool (thread numbers and all), and it sure beats the living hell out of “msbuild” (which I hate like a sickness).
So, I’d be curious to hear whatever tips/tricks people have for getting “build” to build something even slightly modern.
Peter
OSR
David R. Cattley wrote:
In a misguided fit of brazen self delusion I attempted to build a
little bit of UI in a driver project using WTL. MAKFILE.NEW has
long had what seems like good plumbing to bring WTL & ATL into a
usermode build target. The only thing that is missing is about half
of the API header files that WTL is expecting to find J
What did you encounter? I don’t use this every day, but in response to
your post, I just built a sources file for one of my WTL projects, and
it compiled OK with the 7100 WDK. I had this:
USE_LIBCMT=1
USE_STL=1
USE_ATL=1
ATL_VER=70
WTL_INC_PATH=…
USE_WTL=1
I had the WTL includes in …\wtl. (Like DirectShow, I now embed WTL
into every project where I need it.)
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
When using WTL8 and trying to do something with property sheets I
encountered a number of header files that WTL wanted to drag in for controls
(IE / mshtml like stuff) that were not in the WDK API headers.
In principal, yes, the basic guts seemed to compile just fine. I was trying
to be uber-lazy and use the some of the handy control wrappers, DDX, etc.
Truth be told I blew the folder away when I went ‘old-school’ on it and I
should have saved it. That way I could actually make a list of the headers
that were missing.
I guess I should shut-up and go build a simple WTL based UI ‘test’ project
and see what breaks.
For what it is worth, I set WTL_INC_PATH=$(_PROJECT_MK_PATH)<somepath> and
had a copy staged with the project as well.
Cheers,
-dave
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tim Roberts
Sent: Thursday, May 14, 2009 7:21 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] MAKEFILE.NEW USE_WTL - Alas, not really
David R. Cattley wrote:
>
> In a misguided fit of brazen self delusion I attempted to build a
> little bit of UI in a driver project using WTL. MAKFILE.NEW has
> long had what seems like good plumbing to bring WTL & ATL into a
> usermode build target. The only thing that is missing is about half
> of the API header files that WTL is expecting to find J
>
What did you encounter? I don’t use this every day, but in response to
your post, I just built a sources file for one of my WTL projects, and
it compiled OK with the 7100 WDK. I had this:
USE_LIBCMT=1
USE_STL=1
USE_ATL=1
ATL_VER=70
WTL_INC_PATH=…
USE_WTL=1
I had the WTL includes in …\wtl. (Like DirectShow, I now embed WTL
into every project where I need it.)
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Well Tim, I gave up way to early.
It seems as though only richedit.h and richole.h are missing from what I
want to use (compared against the 7100.0.0 WDK).
By adding
C_DEFINES=$(C_DEFINES) /I
I was able to get build/nmake/platform.new to stick the Platform SDK include
path at the end of the include search paths (so as to not interfere with the
preference to include from {OAK|DDK|SDK|CRT}_INC_PATH. After building a
.pp file to see what the pre-processor did and grep’ing out the paths that
intersected with the PSDK include path, I found only those two files
included.
That still seems a bit of a hack but at least that is narrowed down to two
files.
Too bad WTL80 does not break the ‘rich-xxxx’ controls out separately but
that is easily dealt with.
Cheers,
Dave Cattley
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of David R. Cattley
Sent: Thursday, May 14, 2009 8:02 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] MAKEFILE.NEW USE_WTL - Alas, not really
When using WTL8 and trying to do something with property sheets I
encountered a number of header files that WTL wanted to drag in for controls
(IE / mshtml like stuff) that were not in the WDK API headers.
In principal, yes, the basic guts seemed to compile just fine. I was trying
to be uber-lazy and use the some of the handy control wrappers, DDX, etc.
Truth be told I blew the folder away when I went ‘old-school’ on it and I
should have saved it. That way I could actually make a list of the headers
that were missing.
I guess I should shut-up and go build a simple WTL based UI ‘test’ project
and see what breaks.
For what it is worth, I set WTL_INC_PATH=$(_PROJECT_MK_PATH)<somepath> and
had a copy staged with the project as well.
Cheers,
-dave
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tim Roberts
Sent: Thursday, May 14, 2009 7:21 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] MAKEFILE.NEW USE_WTL - Alas, not really
David R. Cattley wrote:
>
> In a misguided fit of brazen self delusion I attempted to build a
> little bit of UI in a driver project using WTL. MAKFILE.NEW has
> long had what seems like good plumbing to bring WTL & ATL into a
> usermode build target. The only thing that is missing is about half
> of the API header files that WTL is expecting to find J
>
What did you encounter? I don’t use this every day, but in response to
your post, I just built a sources file for one of my WTL projects, and
it compiled OK with the 7100 WDK. I had this:
USE_LIBCMT=1
USE_STL=1
USE_ATL=1
ATL_VER=70
WTL_INC_PATH=…
USE_WTL=1
I had the WTL includes in …\wtl. (Like DirectShow, I now embed WTL
into every project where I need it.)
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
OK, I’m confused.
richedit.h and richole.h are both in the WDK - have been since Vista.
Is the problem that the WDK has the wrong version? What am I missing?
Thanks,
Jennifer
Ahah! Wow, I never even looked at the entire WDK inc structure.
But perhaps you could explain why these files are in the inc\ddk subfolder
and not in the inc\api subfolder?
When I build a usermode module MAKEFILE.NEW does not put the inc\ddk
subfolder in the include path.
Maybe that has been my problem all along.
One more layer of the onion peeled back, still smells like an onion…
Thanks,
-dave
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@microsoft.com
Sent: Friday, May 15, 2009 3:45 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] MAKEFILE.NEW USE_WTL - Alas, not really
OK, I’m confused.
richedit.h and richole.h are both in the WDK - have been since Vista.
Is the problem that the WDK has the wrong version? What am I missing?
Thanks,
Jennifer
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer