Thread View: borland.public.cppbuilder.deployment
3 messages
3 total messages
Started by Roee Bachar
Fri, 29 Apr 2005 21:51
deploy exe file
Author: Roee Bachar
Date: Fri, 29 Apr 2005 21:51
Date: Fri, 29 Apr 2005 21:51
7 lines
1000 bytes
1000 bytes
Hi, I'm using BCB V6. How do I deploy only exe file that can run without the need of BCB install on that machine Thanks
Re: deploy exe file
Author: Ed Mulroy [TeamB]
Date: Sat, 30 Apr 2005 13:24
Date: Sat, 30 Apr 2005 13:24
53 lines
3232 bytes
3232 bytes
From the question it seems that your project is built as Dynamic LInked. The compiler's runtime libraries and packages already exist on your machine. The project is built to use those items that are on your machine instead of building their code into your EXE file. To change that, do these things: Under Project|Options|Compiler uncheck "Use dynamic RTL" Under Project|Options|Packages uncheck "Build with runtime packages" Select Project|Build The change above changes the project to Static Linked. Those items from the runtime libraries and packages that are used by the project are built into the EXE. No external DLLs or Packages are needed but the code used from them is now inside the EXE file so it is larger. Note that you do not need to do a BCB install on the other machine to run a dynamic linked program on it. What is needed is for the DLLs and Packages that the program uses to be on the target machine. If you are creating many programs to run on the target machine it usually more efficient to dynamic link so that only one copy of the code from those other items is on the target machine. If only one or two programs are to be on that machine then static linked is most likely the way to go. You can find out what DLLs and packages are needed with a command like this: tdump -em. ProgName.exe (do not overlook the '.' at the end of the '-em.' above) That will give you a list of the DLLs and Packages (tdump calls them 'modules') used by the EXE. Because they can also use such things you need to repeat the command for the DLLs and Packages that are reported to build a full list of what is used. Those needed items would then be placed onto the target machine in some combination of the same directory as the program or in the system path (one of the directory locations shown when you give the command PATH). . Ed > Roee Bachar wrote in message > news:42734723@newsgroups.borland.com... > > I'm using BCB V6. > How do I deploy only exe file that can run without the need of > BCB install on that machine
Re: deploy exe file
Author: Roee Bachar
Date: Mon, 02 May 2005 20:35
Date: Mon, 02 May 2005 20:35
63 lines
3244 bytes
3244 bytes
Thanks Ed It's working Roee "Ed Mulroy [TeamB]" <dont_email_me@invalid.com> wrote in message news:42738705@newsgroups.borland.com... > From the question it seems that your project is built as Dynamic > LInked. The compiler's runtime libraries and packages already exist > on your machine. The project is built to use those items that are on > your machine instead of building their code into your EXE file. > > To change that, do these things: > > Under Project|Options|Compiler > uncheck "Use dynamic RTL" > Under Project|Options|Packages > uncheck "Build with runtime packages" > Select Project|Build > > The change above changes the project to Static Linked. Those items > from the runtime libraries and packages that are used by the project > are built into the EXE. No external DLLs or Packages are needed but > the code used from them is now inside the EXE file so it is larger. > > Note that you do not need to do a BCB install on the other machine to > run a dynamic linked program on it. What is needed is for the DLLs > and Packages that the program uses to be on the target machine. If > you are creating many programs to run on the target machine it usually > more efficient to dynamic link so that only one copy of the code from > those other items is on the target machine. If only one or two > programs are to be on that machine then static linked is most likely > the way to go. > > You can find out what DLLs and packages are needed with a command like > this: > > tdump -em. ProgName.exe > (do not overlook the '.' at the end of the '-em.' above) > > That will give you a list of the DLLs and Packages (tdump calls them > 'modules') used by the EXE. > > Because they can also use such things you need to repeat the command > for the DLLs and Packages that are reported to build a full list of > what is used. > > Those needed items would then be placed onto the target machine in > some combination of the same directory as the program or in the system > path (one of the directory locations shown when you give the command > PATH). > > . Ed > > > Roee Bachar wrote in message > > news:42734723@newsgroups.borland.com... > > > > I'm using BCB V6. > > How do I deploy only exe file that can run without the need of > > BCB install on that machine > >
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads