Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (5)

Resolved PBC standalone compiler - include libraries in exe

  1. How-to
0
Votes
Undo
  1. David Peace (Powersoft)
    David Peace (Powersoft)
  2. PowerBuilder
  3. Tuesday, 10 December 2019 12:44 PM UTC

Hi Guys

I have just realised that the PBC170.exe does not allow the libraries to be included in the EXE file and not generate PBDs. This is fundamental to our deployment strategy so the PBC170.exe is no use to us.

Is there a way t compile the EXE including all the PBLs in the EXE code using orca script?

Cheers

David

Re: Flickering effect while window switching, use...
Using Powerbuilder and Appeon toolkit to develop a...
Accepted Answer
Michael Kramer
Michael Kramer Accepted Answer Pending Moderation
  1. Tuesday, 10 December 2019 13:01 PM UTC
  2. PowerBuilder
  3. # Permalink

Hi David,

Back in PB 11.5 I struggled with OrcaScript since all version-number info from the build project object - and from the ORCA script file - was ignored. Every EXE was version 1.0.0.0.

Not sure whether some strange error condition may leave IDE open...
4-5 employers ago so I can't reproduce to confirm.

Anyways,

  1. Use ORCAScript to get latest
  2. Create CMD file to run the build/deploy
    See PowerBuilder Help
    > Users Guide
    > The PowerBuilder Environment
    > Working with PowerBuilder
    > Building workspaces
    > From a command line
  3. Create MSI file using whatever tools you choose

Doing deploy this way means your workspace including potentially multiple project objects govern the full build/deploy sequence. It worked like a breeze.

HTH /Michael

Comment
René Ullrich
  1. René Ullrich
  2. Wednesday, 11 December 2019 06:21 AM UTC
BTW, you can set version information in OrcaScript using the "set exeinfo property" command.
  1. Helpful
Michael Kramer
  1. Michael Kramer
  2. Wednesday, 11 December 2019 12:29 PM UTC
True, this being back in 2010-2012 I don't recall every detail. As I remember it was SET EXEINFO that failed. Never found out why. I simply chose to deploy workspace via IDE configured via Workspace>Target(s)>Project(s).
  1. Helpful
There are no comments made yet.
Responses (5)
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 10 December 2019 17:02 PM UTC
  2. PowerBuilder
  3. # 1

Hi David,

If I'm understanding correctly what you want to do, by upgrading to PowerBuilder 2019 your issue will be solved.

In PowerBuilder 2019's standalone compiler it accepts a new /pd argument for specifying whether each PBL should be compiled into a PBD/DLL:

• Default is Y, compile to PBD/DLL
• Passed as a series of flags
• one for each PBL in order
• up through the last PBL you want to specify control over

Here are a few examples (assumes 3 PBLs):
• Compiles first and last PBLs as PBD/DLL: /pd YNY
• Compiles everything into executable: /pd NNN
• Compiles first PBL into executable, creates PBDs for other two (because Y is the default): /pd N

This information is courtesy of Bruce Armstrong from his Elevate 2019 conference presentation.  If you were an Elevate 2019 attendee, video recordings of most conference presentations are available in the user center.

Regards,
Armeen
Comment
Load more comments
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Tuesday, 10 December 2019 17:43 PM UTC
Great. Yes PowerBuilder 2019 R3 makes sense since that will be the next LTS (long-term support) version to replace the current LTS version you are using. That would be good upgrade path since it seems your QA process is very heavy.
  1. Helpful
David Peace (Powersoft)
  1. David Peace (Powersoft)
  2. Wednesday, 11 December 2019 11:18 AM UTC
Yes, some of the applications we support are very large and full regression testing is time-consuming.



Can I make a suggestion for an enhancement. It would be good to be able to compile using a project in PB rather than specify the flags on the command line. In order to automate this process we would need to export the project, read the library list and compile the flag list. We build numerous applications via the same code and when a library is added to an application and the project updated we need to identify this in the flags parameter.



There is a compile project option in orca script but that does not work for exe deployment. if the PBC method extracted the data from the project given and prepared the list of PBD flags accordingly this would be much better. If this could come in for 2019R3 that would be fantastic :)



Many thanks

David
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Wednesday, 11 December 2019 11:21 AM UTC
Hi David, great suggestion. Please email to product@appeon.com sp Appeon product management sees it. Thanks.
  1. Helpful
There are no comments made yet.
mike S
mike S Accepted Answer Pending Moderation
  1. Tuesday, 10 December 2019 15:59 PM UTC
  2. PowerBuilder
  3. # 2

i use orcascript to do the builds.  pbc is too limited. 

 

orcasript has a lot of steps in it, and i'm not a huge fan of the way it handle errors.  Powergen is a fantastic option.

Comment
There are no comments made yet.
David Peace (Powersoft)
David Peace (Powersoft) Accepted Answer Pending Moderation
  1. Tuesday, 10 December 2019 14:20 PM UTC
  2. PowerBuilder
  3. # 3

Does the build project work for EXE projects?

Comment
David Peace (Powersoft)
  1. David Peace (Powersoft)
  2. Tuesday, 10 December 2019 15:00 PM UTC
I think I may have answered my own question, NO it does not.
  1. Helpful
There are no comments made yet.
René Ullrich
René Ullrich Accepted Answer Pending Moderation
  1. Tuesday, 10 December 2019 13:32 PM UTC
  2. PowerBuilder
  3. # 4

Hi David,

in "build executable" command of OrcaScript you may specify for each library to create a PBD or not.

Look for "pbdflags" parameter in the help: https://docs.appeon.com/appeon_online_help/pb2017r2/pbug/apbs02.html

HTH,

René

 

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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.