Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to build and install google-url as a shared library on Mac OS/Linux
    primarykey
    data
    text
    <p>I want to use <a href="http://code.google.com/p/google-url/" rel="nofollow">google-url</a> in my project as a shared library on Linux\Mac OS, but can not figure out the right way to build it... </p> <p><strong>Question:</strong> what is the way you suggest to build it from scratch form official sources?<br> Requirements - be able to stay in sync with official repo and use standard(make) tools.</p> <hr> <p>As far as i can see, right now there are few ways to build it:</p> <ul> <li><p>in the <strong>official repo</strong> itself only Visual Studio 2005 build files are included</p></li> <li><p>it is in use at <strong>Chromium</strong> and so <a href="http://src.chromium.org/svn/trunk/src/build/temp_gyp/googleurl.gyp" rel="nofollow">there is .gyp available</a> for it but looks like it is tight integrated with Chromium build structure, so there is no easy way to generate Makefile for the standalone library build.<br> Although it has a comment inside "<em>TODO(mark): Upstream this file to googleurl.</em>"<br> So at list this considered to be possible. </p></li> <li><p>Googleurl is also integrated with <strong>PageSpeed project</strong> in <a href="http://page-speed.googlecode.com/svn/lib/trunk/src/build/temp_gyp/googleurl.gyp" rel="nofollow">.gyp</a> form (thought no the same one as above) and so it is somehow built there</p></li> <li><p>third-party <strong>bindings for python</strong> are available and also contain some <a href="http://code.google.com/p/python-google-url/wiki/HowToBuildGoogleUrlWithLinux" rel="nofollow">build instructions</a>, but with SCons this time, and AFAIK it is kind of obsolete system to rely on.</p></li> </ul> <p>Looks like i'm not the only one with this trouble, so other people i found both just implemented their own build files using autotools: </p> <ul> <li><a href="https://github.com/artemg/Googleurl-separate-library" rel="nofollow">https://github.com/artemg/Googleurl-separate-library</a> </li> <li><a href="https://github.com/commoncrawl/commoncrawl-crawler/blob/master/src/native/src/libGoogleURL/googleurl/README.google" rel="nofollow">https://github.com/commoncrawl/commoncrawl-crawler/blob/master/src/native/src/libGoogleURL/googleurl/README.google</a> </li> </ul> <p>It could work but the filesystem layout is not the same as in official repo/they have local modification so there are no easy way to downstream changes and stay in sync.</p> <p>The most tempting way would be to use GYP to generate platform-specific build files for the oficial repo once: make/xcode/visual studio, then just save and use them later as needed..but i have no idea how to approach this and where to start from.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload