C++ Builder IDE, Debugging IDE Make?

borland.public.cppbuilder.ide -


C++ Builder IDE >> Debugging IDE Make?

by P Buschka » Sun, 12 Oct 2003 02:08:45 GMT

I have a problem that the Builder compiles several files each time I do a
make from within the IDE even if only one .cpp file is changed. Some people
have suggested that the timestamp of some file that the compiled sourcefiles
are dependent on can be erraneous. Well, I looked through all my files and
cannot find any such error, so I wonder if there is some way to see what the
IDE make base its decision to do a compile on? Is there some debug-mode or
debug-option for the built-in make?

Any suggestions to help me solve this annoying problem is welcome.

Thanks in advance
P Buschka



Top

C++ Builder IDE >> Debugging IDE Make?

by Edward Diener » Sun, 12 Oct 2003 03:08:06 GMT





You should be able to export the IDE's make process to a Make file. I am
pretty sure there is a Borland Make option which will give you a rundown of
just what the dependencies are when Make decides to Make a file ( look in
the Make documentation ). If you add that to the exported Make file and then
do a command-line make, you should be able to see why it is building your
several targets.




Top

C++ Builder IDE >> Debugging IDE Make?

by Remy Lebeau (TeamB) » Sun, 12 Oct 2003 03:36:58 GMT






Project | Options | Compiler | Compiling

Enable both "Show General Messages" and "Extended Error Information"


Gambit



Top

Debugging IDE Make?

by Wim Bekker » Mon, 13 Oct 2003 15:38:35 GMT


"Remy Lebeau (TeamB)" < XXXX@XXXXX.COM > schreef in


For more information:

Edit the registry:
\HKCU\Software\Borland\C++Builder\6.0\Compiling.
set ShowCommandLine to 'True'.
this will give you hint information about what command lines are invoked.

Add an '#pragma message ("<MyProgram>: using header: __FILE__")' directive
in your header files to see which header files are used when compiling.

Wim



Top
Similar Threads

1. Icon file not displaying correctly I made in vc ide

2. Debugging of ISAPI DLL's made easier

3. Pervasive ntdll.DbgBreakPoint makes debugging my OPC exe server impossible (DCOM/OleAutomation)

4. Delphi 8 .Net IDE making me sick 

Ok,

Everytime I compiled and run something in the Delphi 8 .NET ide... and I
stop/exit the program my IDE is totally fucked up !

Now I know Delphi 8 .Net is like BETA SHIT... it needs a LOTTTTTTTTTTTTT OF
IMPROVEMENT :)

But still it's cool.

So... how can I prevent Delphi 8.NET from Resizing my Code Editor...

I want delphi to STOP fucking around with my WINDOWS/SCREEN LAYOUT !

:)

Maybe I should install the Updates etc ?

Gjjjjeeeeeeeeeeeeeezus man D8NET is 100x times less good as D8WIN32 IDE

5. BDS2007 - breakpoint in Debugger makes IDE Disappear. - C++ Builder IDE

6. How to make Debug.Assert() behave like a breakpoint in the IDE 

I would expect that Debug.Assert() would break into the IDE and stop
on the relevant line of code and highlight it. But instead I get a
dialog asking if I want to abort or ignore etc.

How can I get the behavior I expected?

7. compile and debug a single .cs in IDE? - CSharp/C#

8. compile and debug a single .cs in IDE? 

Hi Nicholas,

I'm not the using the .cs directly, however I compiled it with csc.exe
to a library (a dll) and refrenced this dll from other projects. So
still can't set a breakpoint on the single .cs even I've loaded it in
IDE with consumer project.

Regards,
Afshar


Nicholas Paldino [.NET/C# MVP] wrote:
> Afshar,
>
>     No, you can not do that, you have to load the project that the CS file
> is included in and then run the executable which makes reference to the
> assembly.
>
>     Hope this helps.
>
>
> --
>           - Nicholas Paldino [.NET/C# MVP]
>           -  XXXX@XXXXX.COM 
>
> "Afshar" < XXXX@XXXXX.COM > wrote in message
> news: XXXX@XXXXX.COM ...
> > Hi Group,
> > Can I compile and  debug a single .cs in IDE?
> > I want to set a breakpoint on my single .cs (in IDE) and call its
> > method from other projects. This .cs is compiled to a dll every time
> > and added to other projects. And compile it directy, NOT  by csc.exe.
> >
> > Regards,
> > Afshar
> >