1. Stefan Malkwitz
  2. PowerBuilder
  3. Wednesday, 28 March 2018 07:41 AM UTC

Hello,

We have a small problem with the pbc170.exe Compiler. We included in our project the pbdom170.pbd (c:\program files (x86)\appeon\shared\powerbuilder\pbdom170.pbd).
If we compile the project in the Powerbuilder2017 IDE everything works as it should.
But if i copy the shown PBC runtime parameters out of the text box und run it in a command window, we get an error.
Any ideas how to fix that? Maybe exclude some librarys or something?

###############################
### Library List of the target:
t:\indiv\pbcompile\pb2017\company1\project1\project1_expert.pbl;
t:\indiv\pbcompile\pb2017\map_libs\map80_1.pbl;
t:\indiv\pbcompile\pb2017\map_libs\map80_1e.pbl;
t:\indiv\pbcompile\pb2017\map_libs\map80_2.pbl;
t:\indiv\pbcompile\pb2017\map_libs\map80_2e.pbl;
t:\indiv\pbcompile\pb2017\map_libs\map80_3.pbl;
t:\indiv\pbcompile\pb2017\map_libs\map80_3e.pbl;
t:\indiv\pbcompile\pb2017\map_libs\map80_6.pbl;
t:\indiv\pbcompile\pb2017\map_libs\map80_6e.pbl;
t:\indiv\pbcompile\pb2017\map_libs\pbs52_2.pbl;
t:\indiv\pbcompile\pb2017\map_libs\pbs52_3.pbl;
t:\indiv\pbcompile\pb2017\map_libs\pbs52_5.pbl;
t:\indiv\pbcompile\pb2017\map_libs\schedule.pbl;
t:\indiv\pbcompile\pb2017\fus_libs\fus_search_extender.pbl;
t:\indiv\pbcompile\pb2017\fus_libs\fus_trs.pbl;
t:\indiv\pbcompile\pb2017\fus_libs\fus_pnls.pbl;
t:\indiv\pbcompile\pb2017\fus_libs\fus_tooltips.pbl;
t:\indiv\pbcompile\pb2017\fus_libs\fus_ole.pbl;
t:\indiv\pbcompile\pb2017\fus_libs\fus6_map.pbl;
t:\indiv\pbcompile\pb2017\fus_libs\fus_iwh_xplr.pbl;
t:\indiv\pbcompile\pb2017\fus_libs\fus_iwh_xplr_maint.pbl;
t:\indiv\pbcompile\pb2017\fus_libs\fus_iwh_xplr_copy.pbl;
t:\indiv\pbcompile\pb2017\fus_libs\fus_sec_xplr.pbl;
t:\indiv\pbcompile\pb2017\fus_libs\fus_frm_maint.pbl;
t:\indiv\pbcompile\pb2017\fus_libs\fus_mdt_xplr.pbl;
t:\indiv\pbcompile\pb2017\fus_libs\fus_dw_srvc.pbl;
t:\indiv\pbcompile\pb2017\company1\project1\multiprint.pbl;
t:\indiv\pbcompile\pb2017\fus_libs\z_cpp.pbl;
t:\indiv\pbcompile\pb2017\company1\shared\mona_expert_shared_dialog.pbl;
t:\indiv\pbcompile\pb2017\company1\shared\project1_expert_batch.pbl;
t:\indiv\pbcompile\pb2017\company1\shared\project1_expert_shared_dialog.pbl;
t:\indiv\pbcompile\pb2017\company1\shared\project1_expert_shared_xplr.pbl;
t:\indiv\pbcompile\pb2017\company1\shared\project1_expert_ddw.pbl;
t:\indiv\pbcompile\pb2017\company1\project1\project1_expert_bundles.pbl;
t:\indiv\pbcompile\pb2017\company1\project1\project1_expert_dspo.pbl;
t:\indiv\pbcompile\pb2017\company1\project1\project1_expert_obj.pbl;
t:\indiv\pbcompile\pb2017\company1\project1\project1_expert_ftfw.pbl;
t:\indiv\pbcompile\pb2017\company1\project1\project1_expert_lfv_showprot.pbl;
t:\indiv\pbcompile\pb2017\company1\project1\project1_expert_lfv_xplr.pbl;
t:\indiv\pbcompile\pb2017\company1\project1\project1_expert_lfv_dialog.pbl;
t:\indiv\pbcompile\pb2017\company1\project1\project1_expert_lfv_soz.pbl;
t:\indiv\pbcompile\pb2017\company1\project1\project1_expert_lvs_wanf.pbl;
t:\indiv\pbcompile\pb2017\company1\project1\project1_expert_lvs_mntr.pbl;
t:\indiv\pbcompile\pb2017\company1\project1\project1_expert_ppl.pbl;
t:\indiv\pbcompile\pb2017\company1\project1\project1_expert_smmlavis.pbl;
t:\indiv\pbcompile\pb2017\company1\project1\project1_expert_mdt_maint.pbl;
t:\indiv\pbcompile\pb2017\company1\project1\project1_mobil.pbl;
t:\indiv\pbcompile\pb2017\company1\project1\project1_expert_lfv_admin.pbl;
t:\indiv\pbcompile\pb2017\company1\project1\project1_expert_lfv_batch.pbl;
t:\indiv\pbcompile\pb2017\company1\project1\project1_expert_lfv_print.pbl;
t:\indiv\pbcompile\pb2017\company1\project1\project1_expert_lvs_batch.pbl;
t:\indiv\pbcompile\pb2017\company1\project1\project1_expert_lfv_inventur.pbl;
t:\indiv\pbcompile\pb2017\company1\shared\project1_expert_data_ax.pbl;
t:\indiv\pbcompile\pb2017\company1\shared\project1_expert_trns_ax.pbl;
t:\indiv\pbcompile\pb2017\company1\project1\printserver.pbl;
c:\program files (x86)\appeon\shared\powerbuilder\pbdom170.pbd;


###################
### Command line call:
"C:\Program Files (x86)\Appeon\Shared\PowerBuilder\pbc170.exe" /d "t:\indiv\pbcompile\pb2017\company1\project1\project1_expert.pbt" /o "t:\indiv\pbcompile\pb2017\company1\project1\project1_expert.exe" /r "t:\Entwicklung\res.pbr" /w n /f /m n /x 32 /bg y /p "PowerBuilder Enterprise Series" /cp "Sybase, Inc." /de "Sybase, Inc. Product File" /v "1.0.0.1" /fv "1.0.0.1" /ge 0 


###################
### Error we get:
Library 't:\indiv\pbcompile\pb2017\company1\project1\C:\\Program Files (x86)\\Appeon\\Shared\\PowerBuilder\\pbdom170.pbd' failed to open


it looks like the pbc compiler messed things up.

 

Thank you in advance
Stefan Malkwitz

Accepted Answer
Bruce Armstrong Accepted Answer Pending Moderation
  1. Wednesday, 28 March 2018 20:57 PM UTC
  2. PowerBuilder
  3. # Permalink

Try putting the PBD in a different location, preferably one under the workspace directory.  The compiler is likely having problems resolving the relative reference.

I've done compiles with open source pfc projects, which also references that pbdom pbd, and they've worked fine.

Comment
  1. Stefan Malkwitz
  2. Wednesday, 11 April 2018 08:07 AM UTC
Hello Bruce,



Im back from vacation.  Thanks for your answer. I tried it and it works now. 



I moved the "pbdom170.pbd" into the projectfolder and updated my librarylist in the target. Everything works now as it should. No more errors or warnings.



Many Thanks



Regards Stefan



 



 





---------------Sprache erkennenAfrikaansAlbanischAmharischArabischArmenischAserbaidschanischBaskischBengalischBirmanischBosnischBulgarischCebuanoChinesisch (traditionell)Chinesisch (vereinfacht)DänischDeutschEnglischEsperantoEstnischFilipinoFinnischFranzösischGalicischGeorgischGriechischGujaratiHaiti-KreolischHaussaHawaiischHebräischHindiHmongIgboIndonesischIrischIsländischItalienischJapanischJavanischJiddischKannadaKasachischKatalanischKhmerKirgisischKoreanischKorsischKroatischKurdischLaotischLateinLettischLitauischLuxemburgischMadagassischMalaiischMalayalamMaltesischMaoriMarathiMazedonischMongolischNepalesischNiederländischNorwegischNyanjaPaschtuPersischPolnischPortugiesischPunjabiRumänischRussischSamoanischSchottisches GälischSchwedischSerbischShonaSindhiSinghalesischSlowakischSlowenischSomaliSpanischSuaheliSüd-SothoSundanesischTadschikischTamilTeluguThailändischTschechischTürkischUkrainischUngarischUrduUsbekischVietnamesischWalisischWeißrussischWestfriesischXhosaYorubaZuluDeutsch











 













Everything works now as it should. No more errors or warnings.







  1. Helpful
There are no comments made yet.
Alfredo Aldama Accepted Answer Pending Moderation
  1. Wednesday, 28 March 2018 19:08 PM UTC
  2. PowerBuilder
  3. # 1

Hi,

Muestro un PBT

Save Format v3.0(19990112)
@begin Projects
 0 "1&pro&appeon_mobile_demo.pbl";
@end;
appname "appeon_mobile_demo";
applib "appeon_mobile_demo.pbl";
LibList "appeon_mobile_demo.pbl;appeon_samples.pbl;appeon_workarounds.pbl;..\\..\\Program Files (x86)\\Appeon\\Shared\\PowerBuilder\\pbdom170.pbd";
type "pb";

 

##################################

Ahi el PBT no indica que esta en "C:" o en "t:" ; quiza el compilador desde linea de comando lee el PBT pero no sabe que tiene que cambiarse de drive

 

Tu aplicación esta en "t:" 

###################
### Error we get:
Library 't:\indiv\pbcompile\pb2017\company1\project1\C:\\Program Files (x86)\\Appeon\\Shared\\PowerBuilder\\pbdom170.pbd' failed to open

tengo la impresioón que en el PBT no le dice estó está en "C:" 

Regards! 

 

 

 

 

Comment
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 28 March 2018 15:45 PM UTC
  2. PowerBuilder
  3. # 2

Hi Stefan;

   Are you using the latest PB2017R2 software build #1769?

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