Re: Adding SDK

More problems...this application doesn't wanna be created....

Following your advices and instructions...I've tried to create on VS2005 a
project....

C++/Smart Device/ Win32 smart Device Project....when I do that I have an
error window: "Error retrieving information from uyser datastore"
I've looked for it on on-line help and it says that the problems is that
this error occurs when the datastore has become corrupted. I should re-create
a new datastore followind help intructions
(http://msdn.microsoft.com/en-us/library/ms184403.aspx).

I've looked for Corecon folder but if I delete all of the contens (5.01 e
1.0 folder which contain libraries) and restart VS2005 the only answer I get
is another error: "Non registered interface".

I don't know what I could do... :(

At this point I've decided to create the project on Platform Builder...I
choose a Simple Windows CE application (more exactly "WCE Application" and
after a "Simple windows CE Application"). If I try to choosse sources project
Platform Builder doesn't make me see the created project...???? So, I chose
Workspace project and PB created it...

The question I have at this point is: I add my .c main file as sources, on
Right button Settings menu I add "Include Directories" with .h files for
compiler but...I don't know how to add the .lib file for linker because on
link menu, additional libraries I find "coredll.lib" ,I try to add my .lib
separated by semicolon but I obtain an error, I try to separate them with a
point and I doesn't give me and error....but there is another problem now...

When I want to build my project...

BUILD: [Thrd:Sequence:Type ] Message
BUILD: [00:0000000000:PROGC ] Checking for
\WINCE500\sdk\bin\i386\srccheck.exe.
BUILD: [00:0000000001:PROGC ] SrcCheck exit code: 0 (dec).
BUILD: [00:0000000002:PROGC ] Compile and Link for ARM.
BUILD: [00:0000000003:PROGC ] Loading
C:\WINCE500\PBWorkspaces\2443_121108\rifd\Build.dat.
BUILD: [00:0000000004:PROGC ] Done.
BUILD: [00:0000000005:PROGC ] Computing include file dependencies:
BUILD: [00:0000000006:PROGC ] Checking for SDK include directory:
C:\WINCE500\sdk\ce\inc.
BUILD: [00:0000000007:PROGC ] Scan \WINCE500\PBWorkspaces\2443_121108\rifd\
BUILD: [00:0000000010:PROGC ] Linking
\WINCE500\PBWorkspaces\2443_121108\rifd\ directory.
BUILD: [01:0000000017:ERRORE] NMAKE : U1073: don't know how to make
'C:\WINCE500\PBWorkspaces\2443_121108\WINCE500\smdk2443_ARMV4I\cesysgen\sdk\lib\ARMV4I\retail\coredll.lib'
BUILD: [01:0000000019:ERRORE] NMAKE.EXE -i -c BUILDMSG=Stop. LINKONLY=1
NOPASS0=1 failed - rc = 2
BUILD: [00:0000000020:PROGC ] Files Warnings
Errors
BUILD: [00:0000000021:PROGC ] Midl 0 0
0
BUILD: [00:0000000022:PROGC ] Resource 0 0
0
BUILD: [00:0000000023:PROGC ] Message 0 0
0
BUILD: [00:0000000024:PROGC ] Precomp Header 0 0
0
BUILD: [00:0000000025:PROGC ] C/Cpp/Cxx 0 0
0
BUILD: [00:0000000026:PROGC ] Assembler 0 0
0
BUILD: [00:0000000027:PROGC ] Static Libraries 0 0
0
BUILD: [00:0000000028:PROGC ] Dll's 0 0
0
BUILD: [00:0000000029:PROGC ] Exe's 0 0
0
BUILD: [00:0000000030:PROGC ] Resx 0 0
0
BUILD: [00:0000000031:PROGC ] Csharp Targets 0 0
0
BUILD: [00:0000000032:PROGC ] Other 0 0
2
BUILD: [00:0000000033:PROGC ]
BUILD: [00:0000000034:PROGC ] Total 0 0
2
BUILD: [00:0000000035:PROGC ]
BUILD: [00:0000000036:PROGC ] 0 Warnings, 2 Errors
Build for Windows CE (Release) (Built on Apr 14 2005 13:54:39)
File names: Build.log Build.wrn Build.err Build.dat

2443_041108 - 2 error(s), 0 warning(s)



I've explain to you the exact step I follow because I don't actually know
how to risolve these problems...I don't find a solution!

Thanks a lot! You're helping me so much....I'm getting crazy with this kind
of problems 'cause they're not code problems...


Best regards!

"Paul G. Tobey [eMVP]" wrote:

If you're building it as part of building the OS, you don't have to install
the SDK. I prefer sources projects myself and find them easy to edit to add
weird directories for other pieces that you need. However, for many
application types, building the application in Platform Builder is a bad
idea to me. Managed code projects, C# or VB.NET, I would never do that way.
Projects using MFC, ATL, or other large class libraries I would not do that
way. In fact, most projects I would not do this way. On our devices, ONLY
those things that absolutely have to be in nk.bin are in nk.bin. Everything
else is stored in a flash filesystem, on a storage card, or somewhere else,
where it can easily be debugged, updated, or moved.

If you want to build this application from Platform Builder, create your
Subproject and select suitable settings. In particular, I would NOT choose
Empty Project at this point. If your source code currently uses WinMain()
as its entry point, choose Hello, World application and, once the project
has been generated, replace the main .c file generated by the wizard with
yours. If your entry point is main(), choose Simple Windows CE application
and, again, after the project is generated, replace the main .c file with
your own.

Once you have the subproject in what looks like a buildable state,
right-click on it and choose Build. This should both compile and link the
project, and copy the target file <yourproject.exe> to the "flat release
directory", and do a makeimg operation to build the OS with the new file in
it. The project's BIB file, in the Parameter Files folder under the
subproject, should look for it there. My guess is that the Empty Project
option is not setting the build options correctly to copy the output of the
build of the project to the flat release folder or something of that sort.

Paul T.


You want to do File | New | Project in
VS2005. In the dialog that's presented, you want to choose Visual C++ |
Smart Device and the type of project you want. The wizard will then show
another dialog. Select Platforms. You should see your new SDK platform
in
the list. Add it to the supported platforms. Choose Application
Settings
and make suitable entries for what you're trying to do. Click Finish.
This
will generate a stand-alone, application solution targeted at your
device.

.

Relevant Pages

  • Re: client -server interaction over XML supporting multiple protocols
    ... > analyzing various models to develop the server. ... The Windows WinInet at just the socket layer is also very ... expected to be different for each platform. ... will the XML size constraints significantly hinder the request ...
    (comp.lang.cpp)
  • Re: Any Clojure users here?
    ... Each platform has distinct libraries for things like ... But a CL implementation can (and does, in fact, for certain libraries) ... I later want to port it to Windows and give it a native Windows GUI, ...
    (comp.lang.lisp)
  • Re: It is almost certain now, INTEL will have 64bit x86 !!
    ... >>IA64 boxes, and then support them on the 8086, on to of the original ... Its difficult to see what future the Windows on IPF port has ... Windows on Itanium was always more of a marketing exercise allowing ... But the introduction of Windows on AMD64 and Intels new platform ...
    (comp.os.vms)
  • Re: D3 Windows to D3 Linux
    ... migrate from D3 Windows v9 to Linux. ... Linux to be a better platform. ... I'm not trying to speak in favor of this platform or any other - ...
    (comp.databases.pick)
  • Re: Checking for Modification to a Set of Files
    ... use .NET on anything other than Windows for production use. ... production applications, but I may have missed your point. ... platform for anything but a Windows system. ...
    (comp.programming)