On Fri, Mar 1, 2013 at 11:34 AM, Graeme Geldenhuys
wrote:
> On 2013-03-01 14:09, Marcos Douglas wrote:
>>
>> You probably right, but problems can happen -- little problems -- like
>> a file deleted, file renamed, etc. So I'll have to change the lpk
>> anyway, manually.
>
> You should still not get
On 2013-03-01 14:09, Marcos Douglas wrote:
>
> You probably right, but problems can happen -- little problems -- like
> a file deleted, file renamed, etc. So I'll have to change the lpk
> anyway, manually.
You should still not get any conflicts in the *.lpk files even if files
was added, renamed
On Thu, Feb 28, 2013 at 5:51 PM, Graeme Geldenhuys
wrote:
> On 2013-02-28 18:31, Marcos Douglas wrote:
>>> You can change the output directory of the third party package to use
>>> > the $(FPCVer) macro. For example
>>> > "lib/$(FPCVer)/$(TargetCPU)-$($TargetOS)".
>> Yep, but for this I need to ch
On 28 February 2013 19:08, Marcos Douglas wrote:
> On Thu, Feb 28, 2013 at 4:02 PM, Frank Church wrote:
>> On 28 February 2013 17:27, Marcos Douglas wrote:
>>> Hi,
>>>
>>> I would like to know what the best way to work with FPC, Lazarus and
>>> 3rd libs. I will try explain myself:
>>>
>>> Today
On 2013-02-28 19:08, Marcos Douglas wrote:
>
> Yes, but as I said, to do this you need to change the lib package
> (source) to set the output files.
> I do not want change the original libs sources.
But why not? The *.lpk files hardly change. So if you get repository
updates for those packages, t
On 2013-02-28 18:31, Marcos Douglas wrote:
>> You can change the output directory of the third party package to use
>> > the $(FPCVer) macro. For example
>> > "lib/$(FPCVer)/$(TargetCPU)-$($TargetOS)".
> Yep, but for this I need to change lib's sources. I won't to not
> missing the updates, but tha
On Thu, Feb 28, 2013 at 4:02 PM, Frank Church wrote:
> On 28 February 2013 17:27, Marcos Douglas wrote:
>> Hi,
>>
>> I would like to know what the best way to work with FPC, Lazarus and
>> 3rd libs. I will try explain myself:
>>
>> Today I have three FPC versions (2.6.0, 2.6.3 and 2.8.1) and two
On 28 February 2013 17:27, Marcos Douglas wrote:
> Hi,
>
> I would like to know what the best way to work with FPC, Lazarus and
> 3rd libs. I will try explain myself:
>
> Today I have three FPC versions (2.6.0, 2.6.3 and 2.8.1) and two
> Lazarus versions (1.0.1 and 1.1 (trunk))
> The FPC trunk is
On Thu, Feb 28, 2013 at 2:59 PM, Mattias Gaertner
wrote:
> On Thu, 28 Feb 2013 14:27:37 -0300
> Marcos Douglas wrote:
>
>> Hi,
>>
>> I would like to know what the best way to work with FPC, Lazarus and
>> 3rd libs. I will try explain myself:
>>
>> Today I have three FPC versions (2.6.0, 2.6.3 and
On Thu, 28 Feb 2013 14:27:37 -0300
Marcos Douglas wrote:
> Hi,
>
> I would like to know what the best way to work with FPC, Lazarus and
> 3rd libs. I will try explain myself:
>
> Today I have three FPC versions (2.6.0, 2.6.3 and 2.8.1) and two
> Lazarus versions (1.0.1 and 1.1 (trunk))
> The FP
Hi,
I would like to know what the best way to work with FPC, Lazarus and
3rd libs. I will try explain myself:
Today I have three FPC versions (2.6.0, 2.6.3 and 2.8.1) and two
Lazarus versions (1.0.1 and 1.1 (trunk))
The FPC trunk is only for test, so doesn't count.
Both Lazarus were compiled usin
11 matches
Mail list logo
