1. Arcady Abramov
  2. PowerBuilder
  3. Thursday, 24 October 2019 07:23 AM UTC

Hello, all

I am confused with the documentation of Orca script.

It does not state which part of project deploy each command does.

What exactly do the following functions do?

1. Build application - a lot of processing but no PBDs are created

2. Build project - no errors and nothing happens?

3. Build library - can it be done incrementally?

4. Build executable - does not create PBDs

 

Thank you

Arcady

Michael Kramer Accepted Answer Pending Moderation
  1. Thursday, 24 October 2019 12:23 PM UTC
  2. PowerBuilder
  3. # 1

Build options are:

  1. Build app -- This compiles the source code but produces no runtime files.
    1. IDE equivalent: Select a .PBT target in system tree > Right-click > Choose Migrate..., Incremental Build, or Full Build.
    2. Note: ORCA has additional 3-Pass compiler option in case Full Build cannot build the app. This occurs rarely even in very large apps as long as code is well-structured
  2. Build project -- This compiles and generates runtime files as configured by the Project definition.
    1. IDE equivalent: Open project and choose Deploy Project.
  3. Build library -- This compiles and generates runtime library for specific PB library.
    1. IDE equivalent: Select a .PBL library in system tree > Right-click > Choose Build Runtime Library....
  4. Build executable -- This is like build project without the project definition so all config of the executable and dynamic libraries must be defined in the ORCA file.
    1. IDE equivalent: NONE!
    2. I recommend against this because I favor the richness of the project definition.

NOTE: If your first action is "Build app" then the following options simply reuse the already compiled code so they seem to run much faster and do very little.

HTH /Michael

Comment
  1. Arcady Abramov
  2. Thursday, 24 October 2019 12:26 PM UTC
So, why would "Build Project" not create any PBD's?
  1. Helpful
There are no comments made yet.
Arcady Abramov Accepted Answer Pending Moderation
  1. Thursday, 24 October 2019 12:37 PM UTC
  2. PowerBuilder
  3. # 2

Build options are:

  1. Build project -- This compiles and generates runtime files as configured by the Project definition.
    1. IDE equivalent: Open project and choose Deploy Project.

NOTE: If your first action is "Build app" then the following options simply reuse the already compiled code so they seem to run much faster and do very little.

HTH /Michael

 

So, why would "Build Project" not create PBD's or EXE ?

 

Comment
  1. Michael Kramer
  2. Thursday, 24 October 2019 13:06 PM UTC
Do you have a different library list since you last saved your project definition?

If you open project and click Deploy Project, this results in warning that library list has been updated and the deploy aborts.

In ORCA you may not see the same error message but same behavior: Project deploy fails.

You need to open project in IDE. Click Deploy to force project refresh and then save the updated project.

Now I would expect the project deploy to work, also in ORCA.

  1. Helpful
  1. Arcady Abramov
  2. Thursday, 24 October 2019 13:15 PM UTC
I did that. Still, nothing is built. This the script:

//---------------------------

start session

set debug true

set liblist "kiosk.pbl;kiosk_forms.pbl;template.pbl;general.pbl;pos.pbl;ccclient.pbl;myprinters.pbl;crdhndl.pbl;kiosk_setup.pbl;kiosk_rep.pbl;kiosk_reserv.pbl;kiosk_6xx.pbl;day_end.pbl;add.pbl;visual_templates.pbl"

set application "kiosk.pbl" "pos"

build project "kiosk.pbl" "pos_build_unattented"

javascript:void(0);

end session

//---------------------------
  1. Helpful
There are no comments made yet.
John Raghanti Accepted Answer Pending Moderation
  1. Thursday, 24 October 2019 14:54 PM UTC
  2. PowerBuilder
  3. # 3

Are you telling ORCA to build PBDs?

 

start session
BUILD library "c:\programming\office\ms_obj.pbl" "" PBD
BUILD library "c:\programming\office\bug_log.pbl" "" PBD
BUILD library "c:\programming\office\client.pbl" "" PBD
BUILD library "c:\programming\office\funct.pbl" "" PBD
BUILD library "c:\programming\office\invoice.pbl" "" PBD
BUILD library "c:\programming\office\items.pbl" "" PBD
BUILD library "c:\programming\office\misc.pbl" "" PBD
BUILD library "c:\programming\office\purchase.pbl" "" PBD
BUILD library "c:\programming\office\report.pbl" "c:\programming\office\report.pbr" PBD
BUILD library "c:\programming\office\setup.pbl" "" PBD
BUILD library "c:\programming\office\vendor.pbl" "" PBD
BUILD application full
BUILD executable "c:\programming\office\office750.exe" "c:\programming\office\office.ico" "c:\programming\office\bmps.pbr" "NYYYYYYYYYYYY"
end session

Comment
  1. Arcady Abramov
  2. Thursday, 24 October 2019 15:48 PM UTC
I would rather not write 100 lines, if I could use the "build project" statement.

Does anyone have an example of this statement, which actually works, i.e., creates EXE and PBDs ?
  1. Helpful
  1. Michael Kramer
  2. Thursday, 24 October 2019 15:55 PM UTC
I actually had a PowerShell script that used ORCAScript to get latest version but open PB IDE and deploy project using command-line arguments. I had problems with .EXE generated by ORCA that it was always version 1.0.0.0 - and I was builing version 7.4.x of the product.
  1. Helpful
There are no comments made yet.
Arcady Abramov Accepted Answer Pending Moderation
  1. Thursday, 24 October 2019 17:30 PM UTC
  2. PowerBuilder
  3. # 4

So, to summarize:

"Build project" orca script command does not have any examples in the help and I could find none online.

All attempts to use this command by me so far failed: no exe or PBDs are created.

 

Question: Can Appeon support provide a working example of a script containing this command?

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.