Re: [webkit-dev] WebCore/platform standalone library

2017-01-14 Thread Myles C. Maxfield
The ar utility isn’t a linker - it just collects object files. I don’t believe it has any concept of matching symbols up to exported symbols in external shared libraries (like JavaScriptCore for WTF). (But of course someone can correct me if I’m wrong.) —Myles > On Jan 14, 2017, at 1:38 PM,

Re: [webkit-dev] WebCore/platform standalone library

2017-01-14 Thread Darin Adler
> On Jan 14, 2017, at 12:39 PM, Myles C. Maxfield wrote: > > However, a shared library would enforce layering naturally, whereas a static > library would need either an application to link to it and not to WebCore, > such as a unit test suite, or some out-of-band layering

Re: [webkit-dev] WebCore/platform standalone library

2017-01-14 Thread Maciej Stachowiak
> On Jan 14, 2017, at 12:39 PM, Myles C. Maxfield wrote: > > Here’s a quick rundown of where we stand. Please correct me if any of this is > inaccurate. > > There are a few separate issues: > Path on disk of PAL folder: Sounds like everyone more-or-less agrees that >

Re: [webkit-dev] WebCore/platform standalone library

2017-01-14 Thread Myles C. Maxfield
Here’s a quick rundown of where we stand. Please correct me if any of this is inaccurate. There are a few separate issues: Path on disk of PAL folder: Sounds like everyone more-or-less agrees that this should belong in Source/, not in Source/WebCore/. However, I believe this is currently