1. Simone Olianti
  2. PowerBuilder
  3. Wednesday, 12 September 2018 16:07 PM UTC

I have several pbl in my project that are associated to separated resource files (.pbr)

I've noticed that the resource icons listed in the pbr failing to be included when i use the autocompiler. Is there a specific command line option that i need to use to include each PBR file?
The pbr resource associated with the main executable is working fine.

i'm using the /r option to include main pbr like this:
/d "s:\start2\start.pbt" /o "s:\start2\start.exe" /r "s:\pb\icone.pbr"

If i run the compilation from the ide everything working fine

any help would be appreciated,

tia

 

Attachments (1)
Accepted Answer
René Ullrich Accepted Answer Pending Moderation
  1. Wednesday, 29 January 2020 12:15 PM UTC
  2. PowerBuilder
  3. # Permalink

AFAIK the autocompiler doesn't support PBR files for PBLs. It only supports to include ressources into the exe file.

You could use OrcaScript to build your application. It supports to specify the a PBR for a library in the "build library" command.

HTH,

René

Comment
  1. Simone Olianti
  2. Wednesday, 29 January 2020 14:08 PM UTC
interesting, is there an example i could use to generate the executable and related pbds including the pbrs? also is there a way to set the build version? thank you!
  1. Helpful
  1. René Ullrich
  2. Wednesday, 29 January 2020 14:32 PM UTC
This example reads the sources (sr*) from local directory, creates pbls and builds exe.

I have created a small vba script that reads the information from target file and project file to build this Orcascript but you may have a static script.



start session

set debug true

scc set connect property localprojpath "."

scc set connect property logfile "orca.log"

scc connect offline

scc set target "yourapp.pbt" importonly

scc refresh target 3pass

build application full

set exeinfo property companyname "..."

set exeinfo property copyright "..."

set exeinfo property productname "..."

set exeinfo property description "..."

set exeinfo property fileversion "1.0.0.0"

set exeinfo property fileversionnum "1,0,0,0"

set exeinfo property productversion "1.0.0.0"

set exeinfo property productversionnum "1,0,0,0"



build library "your1.pbl" "your_pbr_for_pbl1.pbr" pbd

build library "your2.pbl" "your_pbr_for_pbl2.pbr" pbd

build executable "yourapp.exe" "yourapp.ico" "your_pbr_for_exe.pbr" "yy" newvstylecontrols

scc close

end session



Read the OrcaScript documentation to get information about the parameters! You have to change some parameters (e.g. the "yy")!
  1. Helpful
  1. Simone Olianti
  2. Thursday, 30 January 2020 12:27 PM UTC
thank you working like a charm!!
  1. Helpful
There are no comments made yet.
Simone Olianti Accepted Answer Pending Moderation
  1. Wednesday, 29 January 2020 11:45 AM UTC
  2. PowerBuilder
  3. # 1

hello, looks like i have still problems with PBC170.

the resource images listed in the pbr associated to the single .pbl libraries failing to be included in the compiled .pbd when i use the autocompiler.
The main pbr associated to the main .exe working ok.

i've tried Chris suggestions, but if i omit the images full path inside the .pbr the result is that all of them will be missed even in the main .exe

Also tried to build runtime library without success

any other one having same issue using autocompiler?

Comment
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 12 September 2018 16:29 PM UTC
  2. PowerBuilder
  3. # 2

Hi Simone;

  Do all the images in your PBR's have a folder path specified? if so, that could be the issue ... they should not.

  Also, the PBR (and even the IDE) can have issues including the images. I have to sometimes build an image PBD/DLL manually via the IDE in order to get the images included. It seems to be a "hit and miss" type thing. One time the compile will include the images and sometimes it will not (at least foe me). I reported this issue in PB2017R2.

  So my suggestion would be to try a second PBL (can be empty) where your PBR would load the images into. Make sure your PBR has no image path referenced. If the PBR (or even IDE) compile does not work for that. Try building the PBD/DLL manually, as follows (for example):

Regards ... Chris

 

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.