Re: Wince 6 build

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Thanks for your help but I do have CE_MODULES set to 1. To debug I added a
MESSAGE in the make file and I saw that _COMMONOAKROOT is set to
'C:\WINCE600\OSDesigns\ProjectName\Wince600\BSPNAME_x86\cesysgen\oak'

Is this normal? In the makefile I only include makefile.def (default one).
It seams that I have a problem with my environement variables. This is what
the sources file look like (it's a driver dll):

TARGETNAME=HLDRV
RELEASETYPE=PLATFORM
TARGETTYPE=DYNLINK
DLLENTRY=HlDrvDllEntry

INCLUDES=\
..\..\inc

TARGETLIBS= \
$(_COMMONSDKROOT)\lib\$(_CPUINDPATH)\coredll.lib \
$(_TARGETPLATROOT)\lib\$(_CPUINDPATH)\ceddk.lib \
$(_COMMONOAKROOT)\lib\$(_CPUINDPATH)\Iphlpapi.lib \
$(_COMMONOAKROOT)\lib\$(_CPUINDPATH)\Toolhelp.lib

DEFFILE=HlDrv.def

SOURCES=hldrv.cpp


"Bruce Eitman [eMVP]" wrote:

Check your ceconfig.h file to see if CE_MODULES_IPHLPAPI is set to 1, If it
isn't then you don't have iphlpapi support in your OSDesign. You can back
up from that and check the bat files in Public\CEBASE\oak\misc to see what
it takes to add iphlpapi to CE_MODULES.

--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net

Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member

"Vinz" <Vinz@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DF694C73-A942-4BE5-8AB5-4FA51547CF27@xxxxxxxxxxxxxxxx
The error message is always
NMAKE : U1073: don't know how to make
'E:\IRIS\OS\WINCE600\OSDesigns\PROJECTNAME\Wince600\BSPNAME_x86\cesysgen\oak\lib\x86\debug\Iphlpapi.lib'

But most of the time with my own files. TARGETLIBS in sources files are
built like this: $(_COMMONOAKROOT)\lib\$(_CPUINDPATH)\Iphlpapi.lib. Or
using
$(_TARGETPLATROOT)\lib\$(_CPUINDPATH) path.

I also seen that when I execute a rebuild -c is added to the compiler
options, Is this normal?




"Dean Ramsier" wrote:

You're not going to get a clean build without doing some porting. CEPC
builds because it is already ported.

You didn't post the errors, so there is no way we can diagnose what
you're
missing so far. But it doesn't really matter, you might as well start
the
port since you have to do it anyway.

--
Dean Ramsier - eMVP
BSQUARE Corporation


"Vinz" <Vinz@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:54E0024C-E7F4-4C4A-A7BC-AA602D14D399@xxxxxxxxxxxxxxxx
Hi,

I'm migrating from ce 5 to ce 6. The first step is to change IDE to
VS2005.
I did a lot of changes in include folders and library folders but most
of
the
source code is the same. I know there are changes to be done but I want
to
be
able to compile first. The problem is that when I try to compile my BSP
no
exe or lib files are created and I always receive unresolved externals
for
my
own files. If I create a new project using CEPC BSP it builds
correctly. I
suspect that the linker is never called (and I can confirm this since
there
is no call to link when I build my BSP).

What is be the problem here?






.



Relevant Pages

  • Re: Wince 6 build
    ... beitman AT applieddata DOT net ... the sources file look like: ... The problem is that when I try to compile my ... If I create a new project using CEPC BSP it builds ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Wince 6 build
    ... isn't then you don't have iphlpapi support in your OSDesign. ... I did a lot of changes in include folders and library folders but most ... The problem is that when I try to compile my BSP ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Problems compiling in Platform directory; in Public it works
    ... gal for switch / O ... you need to download and install all QFE's for all installed processors ... Here's my sources file: ... After editing my files I can compile in the Public ...
    (microsoft.public.windowsce.embedded)
  • Help needed creating a BPS with customer .CEC files
    ... I'm using PB5 and am trying to generate the same CE image (except hardware ... specifics) for what is currently 3 differenent x86 based platforms that we ... single project and a custom developed BSP for each of the platforms, ... However it appears that the SOURCES file doesn't ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Problem Cloning PUBLIC directory
    ... you must remove the feature from your platform and ... rebuild, otherwise, the binaries from the old PUBLIC atadisk driver still ... >I fixed the SOURCES file and now everything compiles correctly. ... >>> PlatformBuilder 5.0 and having some problems getting it to compile. ...
    (microsoft.public.windowsce.platbuilder)