On 01/10/2013 22:14, luiz americo pereira camara wrote:
2013/10/1 luiz americo pereira camara <[email protected]
<mailto:[email protected]>>
2013/10/1 Martin <[email protected] <mailto:[email protected]>>
On 01/10/2013 14:14, Martin wrote:
I looked at it. But currently, it looks like it may cause
problems.
Both packages share the same folders, that can lead to
conflicts.
[]
I have added the fcl package. BUT
- The normal package, is kept as it. One package that contains
all, and does not need the fcl package (in fact may have
issues if both are used / not tested)
- The fcl pacage as a separate unit directory. It can be used
INSTEAD of the normal package.
Your worries are pertinents. I hit this problem sometimes.
I haven't looked at this specific package but the best approach is
to create a package that depends only from FCL and create a LCL
package that uses the first one. Most of the time, this can be
done without sharing source paths without much work.
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.
You do NOT need to install, in order to use in projects.
Install is only needed for editor macros.
There are some solutions:
- Put source files of each package in separated folders. As an example
see:
https://code.google.com/p/luipack/source/browse/#svn%2Ftrunk%2Fcairo .
Each package has it's own folder.
I need to keep files easy to sync with the original GIT. Therefore no.
(unless it happens in the original too.)
- Use the same folder for the source and ensure that all files are
added to it's corresponding package. As an example see:
https://code.google.com/p/luipack/source/browse/#svn%2Ftrunk%2Fluicomponents
. Failing to setup properly the package may lead to problems. Recently
i fixed one in
https://code.google.com/p/luipack/source/detail?spec=svn1089&r=1079
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)
- Use the same folder for the source but configure a different unit
output dir. Example
https://code.google.com/p/luipack/source/browse/#svn%2Ftrunk%2Fluidialogs
See above.
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
