![]() |
![]() |
|||||
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
|
Command line options for BCBWhen you run BCB, you can pass it a variety of command line options to control its behavior. These options are documented in the BCB help system. To find the help topic, enter the phrase 'IDE command-line options' in the Help Index. Here is a summary of the most useful options. -np = no default project on startup -ns = no splash screen (does not decrease load time) -dfoo.exe = debug foo.exe -b foo.bpr = build project foo.bpr -m foo.bpr = make project foo.bpr Note: The -b and -m switches exist so that you can compile projects as part of a batch process. In truth, these options are someone limited, and they do not work as well as having a makefile. The problem is that the IDE still appears on the screen as usual, and this takes time. Furthermore, the IDE may prompt you to answer a question. If it does, then the IDE just sits there and waits for you to answer. This may not be the behavior that you want during a batch process. For batch processing, it might make more sense to run make instead. This requires that you have a makefile. In BCB3 and BCB4, the BPR files were makefiles. In BCB5, the BPR is an XML file, which must be converted to makefile if you want to use make. You can convert an XML project file to a makefile using the bpr2mak tool. Also note that project groups (BPG files) are still makefiles. Note: I had not tried the -b flag before writing this tip. Well, after trying it a couple of times, I noticed that BCB5 crashes every time I use it. Keep this in mind before wasting a lot of time on the -b and -m options. | ||||||
All rights reserved. |