Providing support for all E. Crane Computing products, including POWERGEN, PBSERVICE, HARPB, VERSIONEDIT, PBLRESCUE, and PBLEXPLORER.
You are not logged in.
Pages: 1
There seems to be a couple of recent posts on this topic.
Although I can do bootstrap imports and builds where there is a PBD in the library list from the GUI interface, we typically do command-line builds, and the import phase is failing in this instance.
The .GEN file entry looks like this:
$Library="..\pbl\PFC\pbdom\pbdom09.pbd","",1,1,0,".\pbdom.pbg"
as you can see, the 1,1,0 is interpreted as do not regenerate and do not create a PBD, but as stated, this causes a failure in the import when performing a full regeneration after the phase 3 import. The only way to avoid this error is to
specify /NRP on the bootstrap import command line, ie.
"D:\PowerGen Professional\pwrgn9.exe" /j=quancargo.gen /pbg /l=d:\Builds\quancargo.log /a=quancargo /h /nrp /q
Unfortunately, the subsequent regen in the build phase generates the same error. And that is where my investigation has stopped.
If anyone could shed some light on the problem I would appreciate it.
Arrrrrgggghh .... don't perform application build with 'create pbd now' checked, then uncheck and perform build again, without extracting from source again. Why? Because in the meantime you've overwritten the pbd in the library list with an empty entry. Doh!
Are you able to get the result you want?
Phil
Yes, thanks.
Pages: 1