I''m currently trying out the trial version; I''m aiming at creating pure C++ code with it, with no additional ctrlvcl (whatever that is) or what not trampling on top of my application. I''m forcing a C++ compile from the project options.
A couple of questions, though:
1) Why does it (BCB) have to be such an idiot and won''t allow me to neither rename the main module, nor move WinMain out of it?
2) What are __InitVCL and __ExitVCL? It gives me linker errors about them if I comment out #include <vcl.h> in the main module. I don''t want BCB to mess around with my code on any level - can''t I just compile it the good old fasioned C++ style (omit the whole vcl portion in this case)
3) How do I group files in the project manager. BC5 has a Source Pool target which basically acts like a virtual folder in the manager''s view. I don''t want all of my 80 source files to be listed in one long succession - that makes them very difficult to follow.
It''s trying in the worse way to make a Windows application.
Start a new project, and see if you can create a ''console application''.
(VCL stands for ''Visual Component Library''. The guy who designed it for Borland got hired by Microsoft to design the GUI API for .Net.)
If you want to make portable application and make a GUI, check out wxWindows.
Start a new project, and see if you can create a ''console application''.
(VCL stands for ''Visual Component Library''. The guy who designed it for Borland got hired by Microsoft to design the GUI API for .Net.)
If you want to make portable application and make a GUI, check out wxWindows.
Thanks! It works.
Another question, though: how do I disable the debugger from debugging programs run outside of the IDE? I don''t want it to run the IDE every time something decides to crash. I messed around with the options, but the disassembler is run regardless everytime some program produces a terminal error.
Another question, though: how do I disable the debugger from debugging programs run outside of the IDE? I don''t want it to run the IDE every time something decides to crash. I messed around with the options, but the disassembler is run regardless everytime some program produces a terminal error.
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement