<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Signature</TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16481" name=GENERATOR></HEAD>
<BODY text=#000000 bgColor=#ffffff>
<DIV dir=ltr align=left><SPAN class=065542420-26062007><FONT face=Arial
color=#0000ff size=2>We build quite a number of plugins for our application
(i.e. separate Delphi projects), plus do a lot of translation and branding work
(I work for a joint venture between Caterpillar and Trimble, and the same
product gets branded differently (logos, splash screens, etc) for the different
parent companies), so we've quite an extensive build process which in part makes
multiple calls to the command line compiler.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=065542420-26062007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=065542420-26062007><FONT face=Arial
color=#0000ff size=2>Plus version numbers, automatically turning assertions
off, setting conditional defines, compiling resource files,
etc.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=065542420-26062007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=065542420-26062007><FONT face=Arial
color=#0000ff size=2>After all that, it then calls InstallShield from the
command line to build the installers.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=065542420-26062007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=065542420-26062007><FONT face=Arial
color=#0000ff size=2>I'll be interested to look into MSBuild, but it would be
quite a job to port our current build script to it.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=065542420-26062007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=065542420-26062007><FONT face=Arial
color=#0000ff size=2>Thanks for the feedback from everybody.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=065542420-26062007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=065542420-26062007><FONT face=Arial
color=#0000ff size=2>Cheers,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=065542420-26062007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=065542420-26062007><FONT face=Arial
color=#0000ff size=2>C.</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
</DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT size=2><FONT
face=Tahoma><B>From:</B> delphi-bounces@delphi.org.nz
[mailto:delphi-bounces@delphi.org.nz] <B>On Behalf Of </B>Stephen
Barker<BR><SPAN class=065542420-26062007><FONT face=Arial
color=#0000ff> </FONT></SPAN></FONT></FONT></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT size=2><SPAN
class=270342906-26062007><FONT face=Arial color=#0000ff>I've never bothered with
the command line compiler before.</FONT></SPAN></FONT></DIV>
<DIV dir=ltr align=left><SPAN class=270342906-26062007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=270342906-26062007><FONT face=Arial
color=#0000ff size=2>What differences in settings do you all make for release
versions?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=270342906-26062007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=270342906-26062007><FONT face=Arial
color=#0000ff size=2>I suppose it gets around the old problem of leaving
datasets open at design time and forgetting to close them before compiling a
release version. That's about all I tend to change, except maybe the internal
version number.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=270342906-26062007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=270342906-26062007><FONT face=Arial
color=#0000ff size=2>regards,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=270342906-26062007><FONT face=Arial
color=#0000ff size=2>Steve</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
</DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT
face=Tahoma><FONT size=2><B>From:</B> Rohit Gupta
[mailto:rohit@cfl.co.nz] <BR><SPAN class=065542420-26062007><FONT
face=Arial color=#0000ff> </FONT></SPAN></FONT></FONT></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>You will have to
install the whole thing. The change is just in their policy. I
have always the command line compiler on another PC for compiling release
versions. :-) I guess they are just telling you the the command
line compiler does not check for rego info.<BR><BR>Conor Boyd wrote: </DIV>
<BLOCKQUOTE
cite=mid:F7C0AA5DD1508F4789E10B6CC9BB75DB89162B@nzc-ap-xch-02.ap.trimblecorp.net
type="cite"><PRE wrap="">Hi,
I'm intending to take advantage of the small change in the BDS2007 license which allows for the installation of the command line compiler to a separate PC for the purpose of executing automated builds.
Has anybody on the list done this already?
Is it simply a matter of copying the command line compiler executable to the other machine, or is there slightly more to it.
Had a quick google on this, and couldn't find much in the way of resources on the subject.
Thanks for any pointers anybody may have.
<FONT face=Arial size=2></FONT></PRE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>