×
Discuss on T24 Installation, Setting up the environment, TC Server, jBOSS, Package & Deployment, etc…
Creating Pack Without source code
- wagdymounir
- Topic Author
- Offline
- New Member
-
Less
More
- Posts: 3
- Thank you received: 0
13 years 2 months ago #11077
by wagdymounir
Creating Pack Without source code was created by wagdymounir
Dear All,
i am trying to create a pack using the DL.DEFINE and the BUILD.CONTROL and i want to deploy the objects only not the source code of my routines.
is there any way to do this.
i am trying to create a pack using the DL.DEFINE and the BUILD.CONTROL and i want to deploy the objects only not the source code of my routines.
is there any way to do this.
Please Log in or Create an account to join the conversation.
- durai611
- Offline
- Elite Member
-
Less
More
- Posts: 300
- Thank you received: 51
13 years 2 months ago #11080
by durai611
Replied by durai611 on topic Re: Creating Pack Without source code
Im not sure is there any option not to copy the source code in DL.DEFINE or BUILD.CONTROL.
You can copy the created object file of the routines to the required area and catalog it.
You can copy the created object file of the routines to the required area and catalog it.
Please Log in or Create an account to join the conversation.
- wagdymounir
- Topic Author
- Offline
- New Member
-
Less
More
- Posts: 3
- Thank you received: 0
13 years 2 months ago #11089
by wagdymounir
Replied by wagdymounir on topic Re: Creating Pack Without source code
Thanks.
Is there any other way to move the developed routines without the source code ?
Is there any other way to move the developed routines without the source code ?
Please Log in or Create an account to join the conversation.
- johnperez
- Visitor
-
13 years 2 months ago - 13 years 2 months ago #11092
by johnperez
Replied by johnperez on topic Re: Creating Pack Without source code
To avoid passing source code, you must use $... files.
The $files are created every time you execute BASIC command. CATALOG command converts "object code" to executable.
If you are using EB.COMPILE "statement", remember that this routine embeds BASIC & CATALOG command
Finally, you can use BUILD.CONTROL to move "object code" from one to another environment. You must create a list with the $ files to move, below there is an example (let's supposed that my list was saved with the name TA.LIST)
6 RELEASE.PATH...... T24.BP
7. 1 PROGRAM.BP..... T24.BP
8. 1. 1 SELECT.CMD.. SL-TA.LIST
9. 1 MV.RESERVED.9..
10. 1 RELEASE.BP..... T24.BP
11. 1 JBCDEV.LIB..... lib
12. 1 JBCDEV.BIN..... bin
Regards
PD: please take into account, the "object code" must be created over the specific operative system. You can NOT move object code from Windows to Linux (for example)
The $files are created every time you execute BASIC command. CATALOG command converts "object code" to executable.
If you are using EB.COMPILE "statement", remember that this routine embeds BASIC & CATALOG command
Finally, you can use BUILD.CONTROL to move "object code" from one to another environment. You must create a list with the $ files to move, below there is an example (let's supposed that my list was saved with the name TA.LIST)
6 RELEASE.PATH...... T24.BP
7. 1 PROGRAM.BP..... T24.BP
8. 1. 1 SELECT.CMD.. SL-TA.LIST
9. 1 MV.RESERVED.9..
10. 1 RELEASE.BP..... T24.BP
11. 1 JBCDEV.LIB..... lib
12. 1 JBCDEV.BIN..... bin
Regards
PD: please take into account, the "object code" must be created over the specific operative system. You can NOT move object code from Windows to Linux (for example)
Last edit: 13 years 2 months ago by johnperez.
Please Log in or Create an account to join the conversation.
- jpb
-
- Offline
- Moderator
-
- retired . . . ¯\_(ツ)_/¯
Less
More
- Posts: 2859
- Thank you received: 650
13 years 2 months ago #11093
by jpb
Replied by jpb on topic Re: Creating Pack Without source code
BCON document says :
====================
PROGRAM.BP
If programs are to be saved, this will be the BP from
which BUILD.CONTROL is expected to get the
programs. This could either be the source codes or in
case of releasing to client, then the $ files can be
selected and saved *
* = Care should be taken to transfer the DL.DEFINE unit in Binary mode, if the $ files are saved as part of the delivery package.
====================
PROGRAM.BP
If programs are to be saved, this will be the BP from
which BUILD.CONTROL is expected to get the
programs. This could either be the source codes or in
case of releasing to client, then the $ files can be
selected and saved *
* = Care should be taken to transfer the DL.DEFINE unit in Binary mode, if the $ files are saved as part of the delivery package.
The following user(s) said Thank You: wagdymounir
Please Log in or Create an account to join the conversation.
Time to create page: 0.041 seconds