PB5.0 SDK build issue - Not Fixed

chrisaudigier_at_hotmail.co.uk
Date: 02/28/05


Date: 28 Feb 2005 04:42:57 -0800

I have read the correspondance from last November about the PB5.0 SDK
Build issue and I thought the work around would fix my problem but it
does not. I have checked in platform.ini after I have sysgened my
platform and I get the sysgen=0 problem in the file. when I change this
to sysgen=1 and run makesdk from the command prompt nothing happens. It
just returns directly to the prompt. It doesn't seem to run the SDK
build at all. If I change the current directory away from the release
directory then I get 'CopyFile failed to copy database file to "\", Err
= 3
 ==> The system cannot find the path specified.'
in the SDK dialog. I have tried installing PB5.0 on a colleague's
machine and everything works fine. No problem creating the SDK at all.
I've removed and re-installed PB on my machine but still no luck. Both
machines are running windows 2000 but my machine has been in use longer
and has had other development systems installed and removed. I'm
guessing that there must be a left over registry setting which is
causing my machine to behave differently but what could it be? Before I
discovered the posting on this subject I did notice that the SDK wizard
behaved differently on the 2 machines. On the working machine the CPU
tab in the SDK configuration dialog was filled in completely and
correctly but on my machine only the CPU was present. I had to check
the tick box and use the edit key to add the configuration.



Relevant Pages

  • Re: Disco.exe?
    ... That's very strange, since it's included in the SDK. ... which has a Command Prompt clicking which opens the command prompt ... Visual Studio 2005 -> Visual Studio Tools is a menu item called Visual ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: running csc from command prompt - csc.exe file not found
    ... > After installing the SDK, you would find the .NET 1.10 Command Prompt ... > just installed .net framework 1.1 sdk on a PC at work. ... then I enter the csc.exe command string to compile ...
    (microsoft.public.dotnet.framework)
  • Re: SDK: CPUs support
    ... > device supports so you need to use whatever CPU their SDK has. ... can't see SDK of my vendor; if I include ARMV4I too, ...
    (microsoft.public.windowsce.platbuilder)
  • Re: SDK: CPUs support
    ... > device supports so you need to use whatever CPU their SDK has. ... can't see SDK of my vendor; if I include ARMV4I too, ...
    (microsoft.public.windowsce.platbuilder)
  • Re: running csc from command prompt - csc.exe file not found
    ... After installing the SDK, you would find the .NET 1.10 Command Prompt ... run csc.exe to compile a C# source file. ...
    (microsoft.public.dotnet.framework)