On Sat, Jan 02 2021, Rafael Sadowski wrote:
> On Sat Jan 02, 2021 at 03:44:22PM +0100, Jeremie Courreges-Anglas wrote:
>> On Tue, Dec 15 2020, Ashton Fagg wrote:
>> > Ping. Updated version attached.
>>
>> BTW upstream provides proper releases upstream, see the zip files at
>> https://github.com/
On Sat, Jan 02, 2021 at 03:44:22PM +0100, Jeremie Courreges-Anglas wrote:
> On Tue, Dec 15 2020, Ashton Fagg wrote:
> > Ping. Updated version attached.
>
> BTW upstream provides proper releases upstream, see the zip files at
> https://github.com/fmtlib/fmt/releases
> Usually I would suggest using
On Sat Jan 02, 2021 at 03:44:22PM +0100, Jeremie Courreges-Anglas wrote:
> On Tue, Dec 15 2020, Ashton Fagg wrote:
> > Ping. Updated version attached.
>
> BTW upstream provides proper releases upstream, see the zip files at
> https://github.com/fmtlib/fmt/releases
> Usually I would suggest using
On Tue, Dec 15 2020, Ashton Fagg wrote:
> Ping. Updated version attached.
BTW upstream provides proper releases upstream, see the zip files at
https://github.com/fmtlib/fmt/releases
Usually I would suggest using said tarballs, but here it doesn't seem to
bring a significant improvement (generatin
Ping. Updated version attached.
Ashton Fagg writes:
> Jeremie Courreges-Anglas writes:
>
>> [...]
>>
>> I think the port as-is is ripe and ready to commit, but I don't know yet
>> if there are ports that might pick this up.
>>
>> [...]
>
> Just following up on this - if anyone is still interest
"Dimitri Karamazov" writes:
> Thanks Ash for working on this. I just needed this for a new port
> and your mail was godsend. I've also build tested the latest update
> for graphics/openimageio for which fmt is a required build dependency.
> I will post openimageio-2.2.9.0 update soon, just need s
On Fri, December 4, 2020 06:01, Dimitri Karamazov wrote:
> Jeremie Courreges-Anglas writes:
>
>
>> [...]
>>
>>
>> I think the port as-is is ripe and ready to commit, but I don't know yet
>> if there are ports that might pick this up.
>>
>> [...]
>>
>
> Just following up on this - if anyone is stil
Jeremie Courreges-Anglas writes:
> [...]
>
> I think the port as-is is ripe and ready to commit, but I don't know yet
> if there are ports that might pick this up.
>
> [...]
Just following up on this - if anyone is still interested in importing
this new port, I have updated it to the latest vers
Jeremie Courreges-Anglas writes:
> [...snip...]
> You have this line:
>
> WANTLIB+= c++ c++abi ${COMPILER_LIBCXX}
>
> "c++ c++abi" *is* the content of COMPILER_LIBCXX when you use
> base-clang, so no need to duplicate it. The contents of COMPILER_LIBCXX
> will change according to
On Mon, Nov 09 2020, Ashton Fagg wrote:
> Jeremie Courreges-Anglas writes:
>
>> Here are some items that need fixing:
tl;dr everything looks good except WANTLIB.
[...]
>> * WANTLIB is off, don't copy/paste it from other ports. You can just
>> copy/paste the suggested WANTLIB line(s) from make
Jeremie Courreges-Anglas writes:
> Here are some items that need fixing:
>
> * You have to adapt the SHARED_LIBS line. In this case the library is
> named "libfmt.so..." so the SHARED_LIB line should be:
>
> SHARED_LIBS =fmt0.0
Addressed.
> Don't bother with adding the original ver
On Sun, Nov 08 2020, Ashton Fagg wrote:
> Ashton Fagg writes:
>
>> Per discussion in the flatbuffers thread (Marc & Jeremie cc'd), here is
>> an updated version of the fmt port. Tested the same way as before.
>>
>> Only changes are some whitespace clean up and the appropriate
>> SHARED_LIBS entry
Ashton Fagg writes:
> Per discussion in the flatbuffers thread (Marc & Jeremie cc'd), here is
> an updated version of the fmt port. Tested the same way as before.
>
> Only changes are some whitespace clean up and the appropriate
> SHARED_LIBS entry.
Fixing a mistake in the SHARED_LIBS entry. WAN
Ashton Fagg writes:
> Just updating this with the latest iteration.
>
> Test issue has been worked around - have confirmed with upstream it
> doesn't really matter. Test suite now passes completely but I will try
> and figure it out when I have more time. The bug is in the test code,
> not the ac
Just updating this with the latest iteration.
Test issue has been worked around - have confirmed with upstream it
doesn't really matter. Test suite now passes completely but I will try
and figure it out when I have more time. The bug is in the test code,
not the actual library code as far as I can
Hello,
I have here a new port for the fmt library for C++.
NOTE: For bonus confusion, there's already a devel/libfmt. Please note
these are *not* the same software. (suggestions on naming appreciated)
fmt (https://github.com/fmtlib/fmt) is a formatting library that
provides an alternative to C++
16 matches
Mail list logo
