search

majintao0131 / yaml-cpp

Automatically exported from code.google.com/p/yaml-cpp
MIT License
0 stars 0 forks source link

Yaml build as an OSX Framework #120

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Building the yaml-cpp library on OSX, via CMake

What is the expected output? What do you see instead?

The expected output is a shared library - however, it would be desired to be 
able to create an OSX Framework to, for example, permit bundling the library 
easily with an application.

What version of the product are you using? On what operating system?

0.2.6, on OSX 10.7

Please provide any additional information below.

Original issue reported on code.google.com by grrus...@googlemail.com on 2 Sep 2011 at 8:10

GoogleCodeExporter commented 9 years ago 
Just as a heads up, *.dylib can be bundled into an OSX application without too 
much effort. Just change the linking on the compiled binary when creating an 
app bundle via install_name_tool. i.e.

install_name_tool -id @executable_path/../Frameworks/libyaml.dylib 
YourApp.app/Contents/Frameworks/libyaml.dylib

install_name_tool -change path/to/your/libraries/libyaml.dylib 
@executable_path/../Frameworks/libyaml.dylib YourApp.app/Contents/MacOS/yourapp

Original comment by Connor.J...@gmail.com on 6 Oct 2011 at 6:02

GoogleCodeExporter commented 9 years ago 
Why not build it as a .a (static library)? That's what I do.

Original comment by sherief....@gmail.com on 11 Jan 2012 at 10:58

GoogleCodeExporter commented 9 years ago 
This issue has moved to github: https://github.com/jbeder/yaml-cpp/issues/120

Original comment by jbe...@gmail.com on 30 Mar 2015 at 1:24