<br><br><div class="gmail_quote">2011/7/14 Mattias Gaertner <span dir="ltr"><<a href="mailto:nc-gaertnma@netcologne.de">nc-gaertnma@netcologne.de</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<u></u>
<div>
<p style="margin: 0px;"><span> </span></p>
<p style="margin: 0px;"> </p>
<div style="margin: 5px 0px;">
<br>
Frank Church <<a href="mailto:vfclists@gmail.com" target="_blank">vfclists@gmail.com</a>> hat am 14. Juli 2011 um 11:24 geschrieben:<div class="im"><br>
<br>
<blockquote style="margin-left: 0px; padding-left: 10px; border-left: 1px solid blue;" type="cite">
<br>
<br>
<div class="gmail_quote">
2011/7/14 Mattias Gaertner <span><<a href="mailto:nc-gaertnma@netcologne.de" target="_blank">nc-gaertnma@netcologne.de</a>></span><br>
<blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<span style="text-decoration: underline;"> </span>
<div>
<p style="margin: 0px;"><span> </span></p>
<p style="margin: 0px;"> </p>
<div style="margin: 5px 0px;">
<br>
Frank Church <<a href="mailto:vfclists@gmail.com" target="_blank">vfclists@gmail.com</a>> hat am 14. Juli 2011 um 10:11 geschrieben:<br>
<br>
<blockquote style="margin-left: 0px; padding-left: 10px; border-left: 1px solid blue;" type="cite">
[...]<br>
<div class="gmail_quote">
<blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="gmail_quote">
<div>
<blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div>
<div>
> If you are using different Lazarus versions but with same components and<br>
> packages, how would you organize separate build directories for the<br>
> different versions, but same source location.<br>
>
</div>
</div>
<div>
There are many ways.<br>
For example use one lazarus config directory for each version<br>
combination and make all package output directories read only. Then the<br>
IDE will put the ppu files into the config directory.<br>
<br>
<br>
</div>
</blockquote>
</div>
<div>
<div>
<br>
Can this be achieved via macros?
</div>
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
<p style="margin: 0px;"> </p>
<p style="margin: 0px;">There is no macro to make directories read only. </p>
<div>
<p style="margin: 0px;"> </p>
<p style="margin: 0px;"> </p>
<div style="margin: 5px 0px;">
<blockquote style="margin-left: 0px; padding-left: 10px; border-left: 1px solid blue;" type="cite">
<div class="gmail_quote">
<blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="gmail_quote">
<div>
<br>
For instance I have just posted a blog article on FPC/Lazarus compilaton at <a href="http://devblog.brahmancreations.com/content/build-scripts-for-installing-freepascal-and-lazarus-from-source" target="_blank">http://devblog.brahmancreations.com/content/build-scripts-for-installing-freepascal-and-lazarus-from-source</a>, and what I want to do is to have the build_name variable as available to the IDE.<br>
<br>
e.g if a lazarus build is named lazarus_0920_27001, I would like to use a macro based on the package name as well as the lazarus build name, so the compiler knows that units for zeoslib for instance go to directory /components/lazarus_0920_27001/zeoslib.
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
<p style="margin: 0px;"> </p>
</div>
<p style="margin: 0px;">The solution I gave puts the package files in $(PrimaryConfigPath)/lib/$(PkgName)/something, for example</p>
<p style="margin: 0px;">/components/lazarus_0920_27001/lib/zeoslib</p>
<p style="margin: 0px;"> </p>
</div>
</blockquote>
<div>
<br>
Your solution did not indicate that an every package would have its own directory created for it under the PrimaryConfigPath, I thought they would all be dumped into a single directory.
</div>
</div>
</blockquote>
</div></div>
<p style="margin: 0px;"> </p>
<p style="margin: 0px;">That would be a Delphi mess. Separate output directories is one of the key features of the Lazarus package system. </p>
<p style="margin: 0px;"> </p>
<p style="margin: 0px;"> </p>
<div style="margin: 5px 0px;">
<blockquote style="margin-left: 0px; padding-left: 10px; border-left: 1px solid blue;" type="cite">
<div class="gmail_quote">
<blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div>
<p style="margin: 0px;">[...]</p>
<br>
<p style="margin: 0px;">I added a PkgName.</p>
<div>
<p style="margin: 0px;"> </p>
</div>
</div>
</blockquote><div class="im">
<div>
Is it avaiable in 0.9.30 fixes? Are some of the new 0.9.31 backported to fixes?
</div>
</div></div>
</blockquote>
</div>
<p style="margin: 0px;"> </p>
<p style="margin: 0px;">No. </p>
<p style="margin: 0px;"> </p>
<p style="margin: 0px;"> </p>
<div style="margin: 5px 0px;">
<blockquote style="margin-left: 0px; padding-left: 10px; border-left: 1px solid blue;" type="cite">
<div class="gmail_quote">
<blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div>
<div>
<div style="margin: 5px 0px;">
</div>
</div>What is ConfPath?<br>
<br>
</div>
</blockquote><div class="im">Do ConfPath and PrimaryConfigPath refer to the same thing?
</div><div>
<br><div class="im">
I meant ConfDir and PrimaryConfigPath
</div></div>
</div>
</blockquote>
</div>
<p style="margin: 0px;"> </p>
<p style="margin: 0px;">Yes. </p><div class="im">
<p style="margin: 0px;"> </p></div></div></blockquote><div><br><br>I am trying out the approach now. <br><br>I create a lib directory where the units would normally go and make it write protected.<br><br>Forcing a new lib directory for each package causes dcpcrypt and dcpcrypt_laz to have separate lib folders created for them and cause duplicate unit errors.<br>
Is there some way to work around it? Does Lazarus default to the first one it finds in the units directory?<br><br>ZeosDBO switched to using the units in the 'build' subdirectory so I write protected that directory as well.<br>
<br>Indy revealed a problem with .rst files because utilities processing them may hardcoded to write to lib\ directory<br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div class="im">
<div style="margin: 5px 0px;">
<blockquote style="margin-left: 0px; padding-left: 10px; border-left: 1px solid blue;" type="cite">
<br>
<br>
Is it possible to create new user defined macro variables for the IDE?
</blockquote>
</div><br></div>
Projects and packages can define build macros.<br>
<br>
<br>
Mattias<br>
<br>
</div>
<br>--<br>
_______________________________________________<br>
Lazarus mailing list<br>
<a href="mailto:Lazarus@lists.lazarus.freepascal.org">Lazarus@lists.lazarus.freepascal.org</a><br>
<a href="http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus" target="_blank">http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Frank Church<br><br>=======================<br><a href="http://devblog.brahmancreations.com">http://devblog.brahmancreations.com</a><br>