Hi Patrick,
We haven’t looked at it, but we’ve decided we are interested in making it work
for us.
However, we will still need to keep the VS2010 project files in our tree for
some undetermined amount of time. If you want to start adding a cmake support
windows support for the AppleWin port to
Hi Roger,
did you have some time to look at my example in the meantime?
-- Patrick
Am 11.04.2013 um 00:30 schrieb Roger Fong:
> Hi Patrick,
> A few questions I have about the CMake system, being someone who's never used
> it before.
>
> -I would like to keep all of the unified properties sett
I'm glad to see there is some interest in using CMake to build on windows.
Using CMake has made working on Windows easier for me (thank you Patrick!)...
somewhere on webkit.org there's a page about ideas for making life on windows
easier and I think the CMake build system addresses a number of
Hi Patrick,
On Apr 10, 2013, at 8:12 PM, Patrick Gansterer wrote:
[snip]
>> 1. There's also the Wx port, but they don't seem very interested in
>> switching and it seems the build system is very low maintenance.
>
> There is still a patch at webkit.org/b/73100 for adding CMake files for Wx.
Th
Am 11.04.2013 um 00:30 schrieb Roger Fong:
> Hi Patrick,
> A few questions I have about the CMake system, being someone who's never used
> it before.
>
> -I would like to keep all of the unified properties settings that the VS2010
> property sheets hierarchy provided.
> Can we still maintain th
On Wed, Apr 10, 2013 at 3:30 PM, Roger Fong wrote:
> If my above concerns can be resolved and the example you posted works fine
> for us (I'll try to take a look at it soon), it's probably okay to start
> checking in stuff to get ready for the move to CMake. I don't think we
> really have the reso
Hi everyone:
Sent from my iPhone
On Apr 10, 2013, at 3:30 PM, Roger Fong wrote:
> 2. If you're working on Windows, open up the solution with Visual Studio and
> do work as usual, unless you want to add files in which case you go through
> the CMake scripts again before moving on.
> Woul
Hi Patrick,
A few questions I have about the CMake system, being someone who's never used
it before.
-I would like to keep all of the unified properties settings that the VS2010
property sheets hierarchy provided.
Can we still maintain that through CMake easily?
-How does CMake handle different
Hi,
On Mon, 08 Apr 2013 18:10:29 -0700, Mark Rowe wrote:
On 2013-04-08, at 17:45, Patrick Gansterer wrote:
Hmm, I'll try to set up an example for WTF + JavaScriptCore. Maybe
you can have a look at it then to check if I understand the concept
correctly before I move on to WebCore + WebKit?
S
On 2013-04-08, at 17:45, Patrick Gansterer wrote:
>
> Am 09.04.2013 um 02:29 schrieb Mark Rowe:
>
>>
>> On 2013-04-08, at 17:16, Patrick Gansterer wrote:
>>
>>>
>>> Am 09.04.2013 um 00:58 schrieb Mark Rowe:
>>>
On 2013-04-08, at 15:44, Patrick Gansterer wrote:
>
>>>
Am 09.04.2013 um 02:29 schrieb Mark Rowe:
>
> On 2013-04-08, at 17:16, Patrick Gansterer wrote:
>
>>
>> Am 09.04.2013 um 00:58 schrieb Mark Rowe:
>>
>>>
>>> On 2013-04-08, at 15:44, Patrick Gansterer wrote:
>>>
Am 08.04.2013 um 21:26 schrieb Roger Fong:
> Unfortunatel
On 2013-04-08, at 17:16, Patrick Gansterer wrote:
>
> Am 09.04.2013 um 00:58 schrieb Mark Rowe:
>
>>
>> On 2013-04-08, at 15:44, Patrick Gansterer wrote:
>>
>>>
>>> Am 08.04.2013 um 21:26 schrieb Roger Fong:
>>>
Unfortunately this would cause a lot of complication in our internal bui
Am 09.04.2013 um 00:58 schrieb Mark Rowe:
>
> On 2013-04-08, at 15:44, Patrick Gansterer wrote:
>
>>
>> Am 08.04.2013 um 21:26 schrieb Roger Fong:
>>
>>> Unfortunately this would cause a lot of complication in our internal build
>>> setup that we currently don’t really have the resources to
On Apr 8, 2013, at 3:44 PM, Patrick Gansterer wrote:
>> I wasn’t aware that the build worked without a VS2010 pThreads build. I was
>> running into issues because of the pThreads dll having embedded manifest
>> problems earlier. Did you do anything special to circumvent that issue?
>
> I comm
On 2013-04-08, at 15:44, Patrick Gansterer wrote:
>
> Am 08.04.2013 um 21:26 schrieb Roger Fong:
>
>> Unfortunately this would cause a lot of complication in our internal build
>> setup that we currently don’t really have the resources to deal with right
>> now.
>
> Please don't get me wron
Am 08.04.2013 um 21:26 schrieb Roger Fong:
> Unfortunately this would cause a lot of complication in our internal build
> setup that we currently don’t really have the resources to deal with right
> now.
Please don't get me wrong, but I only get a "some internal problems" answer
always. Can s
.@lists.webkit.org] On Behalf Of Roger Fong
> Sent: Monday, April 08, 2013 3:26 PM
> To: Patrick Gansterer
> Cc: WebKit Development
> Subject: Re: [webkit-dev] Buildsystem cleanup
>
> Unfortunately this would cause a lot of complication in our internal build
> setup that we cu
t-dev-boun...@lists.webkit.org] On Behalf Of Roger Fong
Sent: Monday, April 08, 2013 3:26 PM
To: Patrick Gansterer
Cc: WebKit Development
Subject: Re: [webkit-dev] Buildsystem cleanup
Unfortunately this would cause a lot of complication in our internal build
setup that we currently don't reall
Unfortunately this would cause a lot of complication in our internal build
setup that we currently don’t really have the resources to deal with right now.
It would be nice to unite all the build systems at some point in the future but
we’re going to push this one off for now.
Also we’re plannin
Hi,
since the Chromium code is getting removed step by step I think that the GYP
build system won't have a shiny future in the WebKit repository. In the GYP vs.
CMake match CMake gets an additional point: There is no WebKit port working
with GYP, but at least 3 with CMake. Accordantly to [1] GT
20 matches
Mail list logo
