-
Larry Peters
- PowerBuilder
- Thursday, 7 July 2022 03:08 AM UTC
Building Application Blues:
Being a small organisation with three developers and hence three Appeon licenses we do our building on a separate dedicated PC which does not have an Appeon license and so we use PBC1210.EXE (we are currently using Appeon PowerBuilder 2021 Build 1506) on that PC.
Our build script (for approx 88 PBDs) looks like this:
pbc210.exe /d "F:\PBLINK\PB21\R1234\myapp.pbt" /o "F:\PBLINK\PB21\R1234\myapp.exe" /w n /f /m n /x 64 /bg y /p "My Company" /cp "My Company" /de "My App" /cr "My Company 2018" /v "21.0.0.1506" /fv "1.2.3.4" /ge 2 /le 0 /ps n /pd yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy /rt 21.0.0.1506
Works fine with one exception:
We do not link in our resource files in the EXE. We prefer to link them into a PBD.
In other words, in the project painter, under the Libraries Tab we have all libraries (PBLs) PBD check-boxed with a specified Resource File Name for one of them:
The project, when built using PBC120.EXE does not properly build the PBD with the resource files.
Is there a special setting for this or have we overlooked something in the documentation?
The build script we use is the one automatically generated by the Project Painter at the bottom of the General Tab.
TIA
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.