How to import and compile from *.srd file into library?

[Markus KARG]

We like to use Subversion together with TortoiseSVN.
We're using this couple for all our Java and C++ project for a long
time, and we're doing extensive branche and merge very successfully.
We we want to do this with PowerBuilder 10.2 sources.
We saw that we can import e. g. *.srd files into a library using ORCA
API. But we don't want to spend much time in writing a C based import
tool, so we'd like to just call ORCASCRIPT instead. But there is no
"import from file to library" command in ORCASCRIPT.
So how to import and compile from *.srd file into a library using
ORCASCRIPT?
Or does someone have a ready to use C / ORCA API based tool for doing
"import x.srd,y.srw,z.srf into y.pbl" that takes care of the dependency
between the files to import?

[Bede]

pushOK does it..

In article <448e8384$1@forums-2-dub>, marku...@quipsy.de says...

[Markus KARG]

Bede schrieb:
> pushOK does it..

Obviously this was not the answer to our question, but thank you for the
tip. :-)

[Zsolt Branyiczky]

Hi Markus!

Try this orcascript named import.dat adopted by your demands:

; orcascr100 /d tempdir="%temp%" import.dat
;
; this script is used to create pbls from the source objects
; it works offline, the source objects must be exist before
; this script must be launched from its original pb\config directory

set tempfile = tempdir
set tempfile += "\import_pulika.log"

start session

scc set connect property localprojpath ".."
scc set connect property logfile tempfile
scc set connect property logappend false

scc connect offline

scc set target "..\pulika\pulika.pbt" "refresh_all importonly"

scc exclude liblist
"c:\eaf\v4.0\source\powerbuilder\10.0\server\ext_bo.pbl"
"c:\eaf\v4.0\source\powerbuilder\10.0\server\ext_im.pbl"
"c:\eaf\v4.0\source\powerbuilder\10.0\server\ext_servershared.pbl"
"c:\eaf\v4.0\source\powerbuilder\10.0\shared\ext_shared.pbl"
"c:\eaf\v4.0\source\powerbuilder\10.0\server\eaf_bo.pbl"
"c:\eaf\v4.0\source\powerbuilder\10.0\server\eaf_im.pbl"
"c:\eaf\v4.0\source\powerbuilder\10.0\shared\eaf_proxies.pbl"
"c:\eaf\v4.0\source\powerbuilder\10.0\server\eaf_servershared.pbl"
"c:\eaf\v4.0\source\powerbuilder\10.0\shared\eaf_shared.pbl"
"c:\work\eafextension\pb\proxies.pbl"
"c:\work\eafextension\pb\base_objects.pbl"

scc refresh target "full"

scc close

end session

Exclude libs contains some global pbl libraries, they are not under
source control.

Directory structure used in my pulika project:
pb/config/import.dat
pb/pulika/pulika.pbw
pb/pulika/pulika/pulika.pbt

Regards
Zsolt

[Zsolt Branyiczky]

Sorry, I mistyped the directory structure:

pb/config/import.dat
pb/pulika.pbw
pb/pulika/pulika.pbt

Zsolt

[Bede]

i thought it answered this part:

"...Or does someone have a ready to use C / ORCA API based tool for

doing import x.srd,y.srw,z.srf into y.pbl" that takes care of the
dependency between the files to import?"

In article <448E8C6...@quipsy.de>, marku...@quipsy.de says...

[Markus KARG]

Bede schrieb:

> i thought it answered this part:
>
> "...Or does someone have a ready to use C / ORCA API based tool for
> doing import x.srd,y.srw,z.srf into y.pbl" that takes care of the
> dependency between the files to import?"

If I understand what the pushOK web site tells, then it makes the PB IDE
learn how to talk to SVN. In fact we do not want to open the IDE but we
want to have our standalone compiler server be able to compile our
sources from scratch using ORCASCRIPT. Or is it able to?

Thanks
Markus

[Bede]

no, for that (and other stuff) we're using PowerGen bootstrap import &
building capabilities (in your case you won't need pushOK at all then)

Ben

In article <448EBF71...@quipsy.de>, marku...@quipsy.de says...

[Paul Horan[TeamSybase]]

OrcaScript absolutely CAN do this function. In fact, it was the primary
reason for the introduction of the utility...

Look at the IMPORT_ONLY directive for the Refresh Target command.

Paul Horan[TeamSybase]

"Markus KARG" <marku...@quipsy.de> wrote in message
news:448e8384$1@forums-2-dub...

[Markus KARG]

Actually we want to abstain from buying another product, since ORCA
contains everything we want -- it's 'just' not working as expected.
That's why we hope that some Sybase guy will help us to fix it.

Bede schrieb:

[Markus KARG]

Paul,

thank you, we will try out with the help of another user's sample
script. Actually the ORCASCRIPT documentation is unclear about this
point (there is no point in the documentation clearly saying "This
command imports source code files from your local hard disk into the
specified library", or at least we missed it).
Is ORCASCRIPT taking respect of inter-file dependencies? For example, if
we create an empty library and tell ORCASCRIPT to import all .srd, .srf,
.srw etc. files, does it find out the correct sequence, or do we have to
provide the right sequence ("first import this function, then that
function, then this DW, then that window...")?

Thank You
Markus

Paul Horan[TeamSybase] schrieb:

[Bede]

i see.. when started working here, powergen was already in use, so we
kinda continued with it. don't have much experience with orca, i'm
afraid.

In article <448FA32D...@quipsy.de>, marku...@quipsy.de says...

[Markus KARG]

Bede schrieb:

> i see.. when started working here, powergen was already in use, so we
> kinda continued with it. don't have much experience with orca, i'm
> afraid.

No prob. You tip was worth giving a third party product a try. :-)

Thanks
Markus

[Paul Horan[TeamSybase]]

Yes - OrcaScript is "smart" enough to import all objects in the correct
order.

--
Paul Horan[TeamSybase]
Cynergy Systems
www.cynergysystems.com

"Markus KARG" <marku...@quipsy.de> wrote in message

news:448FA454...@quipsy.de...

[Markus KARG]

Sounds great. I'll try it out as soon as I find the time.
Thanks a lot, meanwhile.
Markus

Paul Horan[TeamSybase] schrieb:

[Alexander Pire]

Remove the first line of the srd file "$PBExportHeader$mydatawindow.srd" put
the rest of the content in a var and use LibraryImport to add the DataWindow
to the PBL.

I have had some problems using the PBORC100.DLL (not in PBORC90.DLL), so I
thing in this case and so far this is a good option to you. Probably not
better than the script you are looking for, but this is another option.

Regards

--

Alexander Pire
PowerObjects
www.powerobjects.com
612.339.3355
**IT Solutions - Outside the Box**

"Markus KARG" <marku...@quipsy.de> wrote in message

news:448e8384$1@forums-2-dub...