1. Olaf Brungot
  2. PowerBuilder
  3. Thursday, 26 October 2017 08:27 AM UTC

Hi, 

Running the AutoCompiler it returns

"Error: Failed to find the library search path in the .pbt file [...path-to-pbt-file] (The liblist statement does not include any .pbl file)."

I've tried to use both the .pbw file and the .pbt, but the result is identical.

Checking in Powerbuilder IDE, the target file does have a complete Library List.

pbc170.exe /d mytarget.pbw

I've also tried to add the PBC runtime parameters from the Powerbuilder IDE, but it returns the same error message.

Building from PowerBuilder IDE is working as expected.

Please advice.

 

 

 

Roland Smith Accepted Answer Pending Moderation
  1. Thursday, 26 October 2017 12:30 PM UTC
  2. PowerBuilder
  3. # 1

I really have no idea why they even bothered to create this app. The already existing ORCAScript tool already has the ability to generate executables without all the limitations.

For example, the new program only supports .pbr files on the exe. It doesn't support .pbr files on a library.

Comment
  1. Aliaksei Hlinski
  2. Friday, 5 January 2018 14:29 PM UTC
because it can be installed on another computer and doesn't require a license. I had the same problem with "Error: Failed to find the library search path in the .pbt file ..." and turned out that my PBL folder was read-only, I've removed read-only flag and the problem is gone

  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 26 October 2017 12:32 PM UTC
  2. PowerBuilder
  3. # 2

Hi Olaf;

  FYI:  There are some key new features and fixes coming to the PBC (PB Compiler) in the new PB 2017 R2 release due out on December 31, 2017. I would personally recommend continuing to use the IDE for the time being for deployment until the new PBC is released.

Regards ... Chris

Comment
  1. Roland Smith
  2. Thursday, 26 October 2017 14:32 PM UTC
Why does it even exist? Under the covers it is doing the same thing that ORCAScript does.

  1. Helpful
There are no comments made yet.
bernd beisel Accepted Answer Pending Moderation
  1. Friday, 10 November 2017 06:57 AM UTC
  2. PowerBuilder
  3. # 3

i had the same problem. the solution was to create a new target file.

 

Regards, BERND

Comment
  1. Paul Doody
  2. Wednesday, 6 December 2017 15:03 PM UTC
I found that targets/workspaces set with read-only attribute caused this issue. Un-setting the attribute allowed the build/compile as expected.

  1. Helpful
  1. Xavier DELAIR
  2. Tuesday, 9 January 2018 10:33 AM UTC
Hello



It seems that the problem comes when the target is on read-only.



 

  1. Helpful
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.