Re: [fpc-devel] FPC internal linker issues with Win64 .a startic-link libraries by GCC newer than 4.8.1

2016-12-12 Thread Sven Barth
Am 12.12.2016 15:09 schrieb "Maciej Izak" : > > > 2016-12-12 14:27 GMT+01:00 Sven Barth : >> >> I'm still thinking about a solution that will satisfy both of our points as good as possible - yes, I already have an idea. Maybe I'll share it this evening when I'm home again. > > > Do you mean : > > =

Re: [fpc-devel] FPC internal linker issues with Win64 .a startic-link libraries by GCC newer than 4.8.1

2016-12-12 Thread Maciej Izak
2016-12-12 14:27 GMT+01:00 Sven Barth : > I'm still thinking about a solution that will satisfy both of our points > as good as possible - yes, I already have an idea. Maybe I'll share it this > evening when I'm home again. > Do you mean : === code begin === TRecordTypeField = packed record //

Re: [fpc-devel] FPC internal linker issues with Win64 .a startic-link libraries by GCC newer than 4.8.1

2016-12-12 Thread Sven Barth
Am 12.12.2016 12:31 schrieb "Maciej Izak" : > > > 2016-12-09 13:49 GMT+01:00 Sven Barth : >> >> Improvements for cppclass are definitely welcome :) > > > Rather not mine :P I have packed cppclass into record. For "wrapped cppclass" I have "default" field (aka proxy record) for direct access combine

Re: [fpc-devel] FPC internal linker issues with Win64 .a startic-link libraries by GCC newer than 4.8.1

2016-12-12 Thread Maciej Izak
2016-12-09 13:49 GMT+01:00 Sven Barth : > Improvements for cppclass are definitely welcome :) Rather not mine :P I have packed cppclass into record. For "wrapped cppclass" I have "default" field (aka proxy record) for direct access combined with "managament operators" to handle "new" & "destroy"

Re: [fpc-devel] FPC internal linker issues with Win64 .a startic-link libraries by GCC newer than 4.8.1

2016-12-09 Thread Sven Barth
Am 09.12.2016 10:32 schrieb "Maciej Izak" : > > > 2016-09-18 2:31 GMT+02:00 Benjamin Rosseaux : >> >> i've noticed a weakness of the FPC internal linker at static-linking .a libraries on the Win64 target, which're generated by GCC newer than 4.8.1, due to the new refptr.* and .refptr.* symbols-can-

Re: [fpc-devel] FPC internal linker issues with Win64 .a startic-link libraries by GCC newer than 4.8.1

2016-12-09 Thread Maciej Izak
2016-09-18 2:31 GMT+02:00 Benjamin Rosseaux : > i've noticed a weakness of the FPC internal linker at static-linking .a > libraries on the Win64 target, which're generated by GCC newer than 4.8.1, > due to the new refptr.* and .refptr.* symbols-can-be-multiple-defined > stuff (inside one single .a

Re: [fpc-devel] FPC internal linker issues with Win64 .a startic-link libraries by GCC newer than 4.8.1

2016-09-17 Thread Benjamin Rosseaux
oh, "then FPC links it with any error." should be "then FPC links it without any error." On Sun, Sep 18, 2016 at 2:31 AM, Benjamin Rosseaux wrote: > Hello, > > i've noticed a weakness of the FPC internal linker at static-linking .a > libraries on the Win64 target, which're generated by GCC newer