Build error(s)

Madhvi, your suggestion worked but I am getting a different error message. Am I missing another env. variable?:

BUILD: [03:0000044205:ERRORE] Error(s) in directory "C:\WINCE700\platform\AM35x_BSP\SRC\test\Tux_PowerManagement\".

BUILD: [03:0000044206:ERRORE] test.obj : error LNK2019: unresolved external symbol GetSystemPowerStatusEx2 referenced in function "int __cdecl DisableStateTimeouts(void)" (?DisableStateTimeouts@@YAHXZ)

BUILD: [03:0000044207:ERRORE] obj\ARMV7\retail\Tux_PowerManagement.dll : fatal error LNK1120: 1 unresolved externals

ERRORE] NMAKE : fatal error U1077: 'C:\WINCE700\sdk\bin\i386\ARM\link.EXE' : return code '0x460'

BUILD: [03:0000044256:INFO ] Stop.

BUILD: [03:0000044257:ERRORE] TargetExeFiles -nologo BUILDMSG=Stop. BUILDROOT=C:\WINCE700\platform\AM35x_BSP CLEANBUILD=1 LINKONLY=1 NOPASS0=1MAKEDLL=1 failed - rc = 2.

Got it, thanks

Hello,

I am new to WinEC7 and the whole platform builder environment.

I am also seeing similar errors after following the quick start guide and the user's guide.

Google is not giving me much, so I ask, what is the name of the file that holds the default build environment variables mentioned above and how do I incorporate it into the newly installed BSP.

If worst comes to worst, I will find the file using my Linux box.

Steven,

The sysgen variables are stored in C:\WINCE700\OSDesigns\<os-name>\<os-name>\<os-name>.pbxml.

Rather than going through the list of variables in the XML file you may find it easier to just load up the sample osdesign in a separate Platform Builder instance, and compare the Catalog Items View with your custom design.

Or you could just copy the sample osdesign workspace and use as a starting point for your own design.

Hope this helps,
Carsten

Carsten,

Thank you for your help.

What I did was created a new project and selected the platform builder type and then selected the installed BSP, AM35x_BSP, and finished. After this I copied and renamed the .pbxml from the installed BSP to the newly created OSDesign. Per the instructions in the BSP user's guide, I should only have to select rebuild solution from the Build menu. After doing this I receive errors.

Do these steps seem consistent with your suggestion above?

Hi Steven,

I would suggest copying an entire sample osdesign, starting from the top level (the directory where the .sln file is located) and use that as a starting point. You can modify the osdesign name/path by editing the .sln workspace file and the .pbxml project file.

If you want to start from scratch however, you can go ahead and create a New Project in Visual Studio, and optionally use the wizard to put something together.

The BSP may require certain OS features to be present, but looking in the quick start guide (A8 02.30.00) I don't see these requirements documented, so your best bet probably is to just select the same Catalog Items that you see in the sample osdesigns, and then once the build succeeds you can start removing features you don't need.

If you prefer a more systematic approach to selecting OS features, open the .pbxml file from the sample osdesign in a text editor and work through the list of sysgen_* variables that you see. Open your custom osdesign in Platform Builder, and in the Catalog Items View you can search for each sysgen to make sure it is included.

Or you could just post the build errors you are seeing - maybe someone will be able to help.

Best regards,
Carsten

Thank you Carsten,

I did a reinstall by copying the files by hand instead of installing the BSP into the WINCEROOT and followed the steps that you gave and the build worked without and other modifications.