Builder 5 no more make files?
Frank Gleeson
and
pillaged my .bpr (make) file.Can this "feature" be turned off? That was
one of the
things I really liked about Builder all the RAD power of VB, plus
implemented
in C++ and a wealth of UNIX-like tools like make and grep.
All of my make information is now stored in an XML file. Are they going
to release a make tool that can read xml? This is the kind of thing that
people in Redmond would do. If Borland wants Kylix to be a success
in linux-land they should not act like M$oft.
Maybe the waves of former VB programmers that Borland expects
to start developing on Kylix will not care. However, existing linux
developers
will not like losing the ability to use makefiles to build there
projects.
I installed Builder 5 to evaluate migrating an existing Builder 4
project.
But since we rely on automated builds as part of our version control
process
I can not recommend using Builder 5.
Rudy Velthuis (TeamB)
> All of my make information is now stored in an XML file. Are they going
> to release a make tool that can read xml?
No. But please read the help on BPR2MAK.EXE:
The BPR2MAK.EXE utility converts XML .BPR project option files to
makefile format for use with the command line tools and is automatically
invoked from the IDE when using the Project|Export Makefile menu option.
Commandline usage
BPR2Mak [[-t<templatefile>] [-o<outputfile> <projectname><.BPR | .BPK>]
[options
--
Rudy Velthuis (TeamB) http://delphi-jedi.org
Frank Gleeson
file then invoke that make -f project.bpr from that file. But what about
version control? Currently the bpr file is under version control. In builder
5 now its strickly an output file. Should I now put the XML file under vc?
I do not know how to read XML, I am comfortable reading makefiles.
Why add this additional obstacle to development? What does XML bring
that justifies these hassles?
Eyal Ben-David
> Well I suppose I could have 1 make script that makes my project.bpr
> file then invoke that make -f project.bpr from that file. But what about
> version control? Currently the bpr file is under version control. In builder
> 5 now its strickly an output file. Should I now put the XML file under vc?
> I do not know how to read XML, I am comfortable reading makefiles.
> Why add this additional obstacle to development? What does XML bring
> that justifies these hassles?
>
I had the same transition BCB4->BCB5. There was no problem with vc.
What is exactly the problem? BCB5 can compile BCB4 bpr projects.
You can always use bpr2mak to view your projects. No problem in XML
in vc too. It is just a text file and very simple to understand
My solution after the transision was as you suggested. I created a new
file 'Makefile' and put it into the version control
# Makefile
#
all: $(PROJECT)
$(PROJECT_MAK): $(PROJECT_BPR)
bpr2mak ...
$(PROJECT): $(PROJECT_MAK)
$(MAKEDIR)\make.exe -f $(PROJECT_MAK)
# etc
#
martin
<rvel...@gmx.de> wrote :
>Frank Gleeson wrote in <3A8F06C6...@netzero.net>...
>
>> All of my make information is now stored in an XML file. Are they going
>> to release a make tool that can read xml?
>
>No. But please read the help on BPR2MAK.EXE:
>
>The BPR2MAK.EXE utility converts XML .BPR project option files to
>makefile format for use with the command line tools and is automatically
>invoked from the IDE when using the Project|Export Makefile menu option.
Just too bad that these makefile don't work sometimes.
--
Martin
What I say is not true; I never speak the truth.
Rudy Velthuis (TeamB)
> Just too bad that these makefile don't work sometimes.
Could you be a bit more precise, or even give an example?
martin
<rvel...@gmx.de> wrote :
>martin wrote in <3a94bc2...@newsgroups.borland.com>...
Sure. I export the makefile, do a make -f project1.mak and I get
this (well almost but the line-wrap messed it up) :
Nice "blah\BIN\..\BIN\" export btw ;-)
MAKE Version 5.2 Copyright (c) 1987, 2000 Borland
C:\PROGRA~1\BORLAND\CBUILD~2\BIN\..\BIN\bcc32 -vGc -vGt -vGd
-Od
-H=C:\PROGRA~1\BORLAND\CBUILD~2\BIN\..\lib\vcl50.csm -Hc -Q
-Vx -Ve
-X- -r- -a8 -b- -k -y -v -vi- -c -tW -tWM -w-par
-I"C:\Program
Files\Borland\CBuilder5\Projects\";C:\PROGRA~1\BORLAND\CBUILD~2\BIN\..\include;C:\PROGRA~1\BORLAND\CBUILD~2\BIN\..\include\vcl
-D_DEBUG;_RTLDLL;NO_STRICT;USEPACKAGES -nobj\ <lots of .CPP
files>
Borland C++ 5.5.1 for Win32 Copyright (c) 1993, 2000 Borland
Error E2266: No file names given
Marc Leclerc
Same error here.
I have a program which is custom built for several customers with different
#define for each of them. Modifying the source and recompiling from the ide
is somewhat time consuming.
"martin" <cha...@xs4all.nl> wrote in message
news:3a961af1...@newsgroups.borland.com...