What I was thinking of doing is finalizing the work necessary to get a
symbol versioning linker script in place, but it is not necessary for this
release. It is just a "nice to have"
So I'd say the lack of such feature won't delay the release.
On Sun, Apr 8, 2018 at 11:37 AM, Nikolaus Waxweiler
Got it working :) Tested with CMake 3.10.2 on Win 10 x64. Version and
copyright information was shown in the details tab of the file
properties dialog.
0001-CMakeLists.txt-Use-ftver.rc-on-Windows.patch
Description: Binary data
___
Freetype-devel
Hi,
I dropped the ball. I meant to get to the symbol versioning stuff we
talked about so we'd have it for this release, but I've been swamped
with work.
Tom
On Sun, Apr 8, 2018 at 9:21 AM, Werner LEMBERG wrote:
>
> > Got it working :) Tested with CMake 3.10.2 on Win 10 x64.
> Got it working :) Tested with CMake 3.10.2 on Win 10 x64. Version
> and copyright information was shown in the details tab of the file
> properties dialog.
Great!
Nikolaus, I've just given you write permission to the FreeType
repositories (user `madleser'). Please commit the CMake stuff,
Oh and, how do you want me to commit the stuff? One big commit or all
nicely broken up?
And by ChangeLog you mean the file, not that I should rewrite my commit
messages?
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
Nikolaus, I've just given you write permission to the FreeType
repositories (user `madleser'). Please commit the CMake stuff,
together with proper ChangeLog entries.
Uh, but my Savannah user name is "morksig"?
___
Freetype-devel mailing list
>> Nikolaus, I've just given you write permission to the FreeType
>> repositories (user `madleser'). Please commit the CMake stuff,
>> together with proper ChangeLog entries.
>
> Uh, but my Savannah user name is "morksig"?
You've apparently registered two names, according to the Savannah user
You've apparently registered two names, according to the Savannah user
management...
Oh. Yes, I vaguely remember something.
By the way, is the "Require.private" thing in the pkg-config file
strictly required?
___
Freetype-devel mailing list
On Sun, Apr 8, 2018 at 6:15 PM, Nikolaus Waxweiler
wrote:
> Oh and, how do you want me to commit the stuff? One big commit or all
> nicely broken up?
>
> And by ChangeLog you mean the file, not that I should rewrite my commit
> messages?
We always duplicate commit messages
> By the way, is the "Require.private" thing in the pkg-config file
> strictly required?
Yes. It ensures that you get all dependencies for static linking.
Werner
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
> Oh and, how do you want me to commit the stuff? One big commit or all
> nicely broken up?
As Alexei answered already: It's basically up to you. However, you've
shown us small chunks, which is good, so simply use them.
> And by ChangeLog you mean the file, not that I should rewrite my
>
11 matches
Mail list logo