Linux destination for shared_library targets is inconsistent with other platforms.

[GoogleCodeExporter]

On Linux, when you build a shared library target, it builds the .so in the 
intermediate directory, but doesn't copy it to product dir like the other 
platforms do.

Original issue reported on code.google.com by gspen...@google.com on 2 Sep 2009 at 11:38

• Merged into: #57

[GoogleCodeExporter]

Actually, it doesn't place it into the intermediate dir, but into some other 
directory 
that doesn't have a variable so it can be referred to.

For instance, if I have a o3d/plugin/plugin.gyp with a target foo, then it 
places the 
.so into [...]/Debug/obj/o3d/plugin/libfoo.so.  The intermediate dir is 
actually 
something like [...]/Debug/obj/plugin/_foo_intermediate, so there's no way to 
reference 
the output file (without a huge hack).

Original comment by gspen...@google.com on 3 Sep 2009 at 12:19

[GoogleCodeExporter]

What generator is this with? I think make and scons should both put the .so 
into 
PRODUCT_DIR/lib/, as per Issue 57.

Original comment by mmoss@chromium.org on 29 Sep 2009 at 8:52

[GoogleCodeExporter]

This is basically a dup of 57; either make this consistent or document the 
difference.  There are larger system 
packaging implications that would need to be hashed out.

Original comment by sgk@chromium.org on 21 Oct 2009 at 5:59

• Changed state: Duplicate