<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote">2013/10/1 Martin <span dir="ltr"><<a href="mailto:lazarus@mfriebe.de" target="_blank">lazarus@mfriebe.de</a>></span><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"><div class="im">
<div>On 01/10/2013 22:14, luiz americo
pereira camara wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote"><div>I looked at the commited files and this configuration
will cause problems when installing both packages. Notice
that is important to allow the installation of the two
packages, in the same IDE. In some projects (a desktop)
may be necessary to use the complete package while in
others (a web service) only the base package is necessary.<br>
<br>
</div>
</div>
</div>
</div>
</blockquote></div>
You do NOT need to install, in order to use in projects.<br>
<br>
Install is only needed for editor macros.<div class="im"><br>
<br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div>There are some solutions:<br>
<br>
</div>
<div>- Put source files of each package in separated
folders. As an example see: <a href="https://code.google.com/p/luipack/source/browse/#svn%2Ftrunk%2Fcairo" target="_blank">https://code.google.com/p/luipack/source/browse/#svn%2Ftrunk%2Fcairo</a>
. Each package has it's own folder.<br>
</div>
</div>
</div>
</div>
</blockquote></div>
I need to keep files easy to sync with the original GIT. Therefore
no. (unless it happens in the original too.)<div class="im"><br>
<br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div>
</div>
<div><br>
- Use the same folder for the source and ensure that all
files are added to it's corresponding package. As an
example see: <a href="https://code.google.com/p/luipack/source/browse/#svn%2Ftrunk%2Fluicomponents" target="_blank">https://code.google.com/p/luipack/source/browse/#svn%2Ftrunk%2Fluicomponents</a>
. Failing to setup properly the package may lead to
problems. Recently i fixed one in <a href="https://code.google.com/p/luipack/source/detail?spec=svn1089&r=1079" target="_blank">https://code.google.com/p/luipack/source/detail?spec=svn1089&r=1079</a><br>
<br>
</div>
</div>
</div>
</div>
</blockquote></div>
Same folder for source does not work, the LCL package will find
fcl-belonging pas files, and use them instead of ppu (even if not
listed in package)<div class="im"><br>
<br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div>- Use the same folder for the source but configure a
different unit output dir. Example <a href="https://code.google.com/p/luipack/source/browse/#svn%2Ftrunk%2Fluidialogs" target="_blank">https://code.google.com/p/luipack/source/browse/#svn%2Ftrunk%2Fluidialogs</a><br>
</div>
</div>
</div>
</div>
</blockquote></div>
See above.<br>
<br></div></blockquote><br></div><div class="gmail_quote">I'm just exposing my experience of 13 years developing with Lazarus and creating / maintaining more than 30 lazarus packages. All the above "designs" works, i can assure. However it's not my intention to say what you should do.<br>
<br>Anyway, i don't use PascalScript and does not know if will work as is now, but if i use it and find some problem i can fix myself.<br><br></div><div class="gmail_quote">Luiz<br></div></div></div>