Summary: | [GTK][EFL] Use CMake to generate Eclipse project files | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Brendan Long <b.long> | ||||
Component: | Tools / Tests | Assignee: | Brendan Long <b.long> | ||||
Status: | RESOLVED DUPLICATE | ||||||
Severity: | Normal | CC: | commit-queue, dbates, eocanha | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Attachments: |
|
Description
Brendan Long
2014-04-23 08:49:09 PDT
Created attachment 229990 [details]
Patch
This just creates an Eclipse project file when you run build-webkit. A more complex version might look for a --create-project argument, or maybe a new Tools/Scripts/create-project script. We can also generate other kinds of projects if we wanted to get into that (--create-project eclipse or --create-project kdevelop). Maybe a new script is the way to do since Apple will eventually want this for XCode?
So that creates a sort of weird project. It looks like the .project and .cproject files need to be at the project root for things to work entirely correctly. Just copying the result works: cp WebKitBuild/Debug/.*project . Running the cmake command against the root folder causes problems because it creates a bunch of files across the build tree, which is fairly annoying. I also ran into an issue where C++11 features were causing trouble (std::function, std::unique_ptr, etc.). I had to manually define __cplusplus=201103L to fix that. Have you seen bug #132190? That patch is already integrated and does what you need if Eclipse is detected. Thanks for the heads up. Glad to see I wasn't the only one who thought of this. *** This bug has been marked as a duplicate of bug 132190 *** |