Board index » cppbuilder » Strange behaviour of mtbcc32

Strange behaviour of mtbcc32


2005-09-01 04:51:46 AM
cppbuilder62
Hi,
As I maintain build files for borland compiler for VCF library I decided
to try mtbcc32 to see if time of compilation will reduce. Instead I get
quite strange results. Basicaly mtbcc32 only compiles if I set equalize
to 1 in ini file. In other case it tries to link every file as dll or
executable.
Any ideas what could be the problem?
Darko
 
 

Re:Strange behaviour of mtbcc32

"Darko Miletic" < XXXX@XXXXX.COM >wrote in message
Quote
As I maintain build files for borland compiler for VCF library I decided
to try mtbcc32 to see if time of compilation will reduce. Instead I get
quite strange results. Basicaly mtbcc32 only compiles if I set equalize
to 1 in ini file. In other case it tries to link every file as dll or
executable.

Any ideas what could be the problem?
mtbcc32, as it is currently built, is intended to be used with the -c
option that causes bcc32 not to link after compile. So, thank you for
reporting this. I will change how it works so that it will automatically
add the -c and then execute the link afterwards, only if the command line
did not include the -c.
Jonathan
 

Re:Strange behaviour of mtbcc32

Jonathan Benedicto wrote:
Quote
mtbcc32, as it is currently built, is intended to be used with the -c
option that causes bcc32 not to link after compile. So, thank you for
reporting this. I will change how it works so that it will automatically
add the -c and then execute the link afterwards, only if the command line
did not include the -c.
The commands do include -c option since they are part of large makefile
that first compiles all cpp files and then assembles them to dll or lib
file. That is why I'm suprised about this behaviour.
Darko
 

{smallsort}

Re:Strange behaviour of mtbcc32

"Darko Miletic" < XXXX@XXXXX.COM >wrote in message
Quote
The commands do include -c option since they are part of large makefile
that first compiles all cpp files and then assembles them to dll or lib
file. That is why I'm suprised about this behaviour.
Yes, then this is suprising. I have VCF, so I'll try and see if I can
replicate this behaviour.
Jonathan
 

Re:Strange behaviour of mtbcc32

Jonathan Benedicto wrote:
Quote
"Darko Miletic" < XXXX@XXXXX.COM >wrote in message
news: XXXX@XXXXX.COM ...

>The commands do include -c option since they are part of large makefile
>that first compiles all cpp files and then assembles them to dll or lib
>file. That is why I'm suprised about this behaviour.


Yes, then this is suprising. I have VCF, so I'll try and see if I can
replicate this behaviour.
Than just in <VCFROOT>\build\bcc open defaulmake.inc and replace CC to
be mtbcc32
That should do it.
Darko
 

Re:Strange behaviour of mtbcc32

"Darko Miletic" < XXXX@XXXXX.COM >wrote in message
Quote
Than just in <VCFROOT>\build\bcc open defaulmake.inc and replace CC to be
mtbcc32

That should do it.
Thank you, I'll do it today.
Jonathan
 

Re:Strange behaviour of mtbcc32

"Darko Miletic" < XXXX@XXXXX.COM >wrote in message
Quote
Than just in <VCFROOT>\build\bcc open defaulmake.inc and replace CC to be
mtbcc32

That should do it.
I'm using the CBX compiler, and I'm getting No files given errors. Bcc is
being told to compile the file "/c", so something is wrong.
Any ideas ?
Jonathan
 

Re:Strange behaviour of mtbcc32

Jonathan Benedicto wrote:
Quote
I'm using the CBX compiler, and I'm getting No files given errors. Bcc is
being told to compile the file "/c", so something is wrong.
As I told you if you put in ini file equalize to 1 than it works OK. I
just do not understand what is the difference here? What does option
equalize do?
Darko
 

Re:Strange behaviour of mtbcc32

"Darko Miletic" < XXXX@XXXXX.COM >wrote in message
Quote
As I told you if you put in ini file equalize to 1 than it works OK. I
just do not understand what is the difference here? What does option
equalize do?
The equalize option start up two threads, then hands each one file. As fast
as each thread compiles the file given, mtbcc32 gives it the next one.
Sounds like something might be wrong with the paths.
Jonathan
 

Re:Strange behaviour of mtbcc32

"Darko Miletic" < XXXX@XXXXX.COM >wrote in message
Quote
As I told you if you put in ini file equalize to 1 than it works OK. I
just do not understand what is the difference here? What does option
equalize do?
Ok, I think I've fixed the problem. You had a /c in the make file that was
causing my app and bcc to think that you wanted /c compiled.
In default.inc, I changed these lines to :
.cpp.obj:
@$(CC) $(CPPFLAGS) -I$(INCDIR) -n$(OBJ) $<
.c.obj:
@$(CC) $(CFLAGS) -I$(INCDIR) -n$(OBJ) $<
Also, mtbcc32 isn't going to help, as the makefile creates a new bcc32
instance for each file individually instead of passing all the files to one
bcc32 instance.
Jonathan
 

Re:Strange behaviour of mtbcc32

Jonathan Benedicto wrote:
Quote
Ok, I think I've fixed the problem. You had a /c in the make file that was
causing my app and bcc to think that you wanted /c compiled.

In default.inc, I changed these lines to :

.cpp.obj:
@$(CC) $(CPPFLAGS) -I$(INCDIR) -n$(OBJ) $<
.c.obj:
@$(CC) $(CFLAGS) -I$(INCDIR) -n$(OBJ) $<

Also, mtbcc32 isn't going to help, as the makefile creates a new bcc32
instance for each file individually instead of passing all the files to one
bcc32 instance.
I see. OK, I'll try to revise makefile in order to get exactly that kind
of behavior.
Thanks for the info.
Darko
 

Re:Strange behaviour of mtbcc32

"Darko Miletic" < XXXX@XXXXX.COM >wrote in message
Quote
I see. OK, I'll try to revise makefile in order to get exactly that kind
of behavior.

Thanks for the info.
You're welcome.
Jonathan