Feeling a bit lost... :\
There isn't a chance this is a 32-bit vs. 64-bit issue right? Probably
not....
This article about Oracle's TOra client I think explains it best... Our
very own MacPorts helper RyanDesigns is the one helping out the OP...
https://github.com/SOCI/soci/issues/89
I'll quote him:
I've found out more about the error message, and though I see you've moved
> on to a solution already, I thought an explanation of what's going on might
> help.
>
>> *I tried to create some simple app using OCI directly and it compiles and
>> it works as expected (the final binary is os x bundle: .app package). I
>> really have no clue what can be wrong...*
>
> Note that there are two unrelated usages of the term "bundle" in OS X.
> You're talking about a folder that the OS X GUI treats as a
> file<http://developer.apple.com/library/mac/#documentation/General/Conceptual/DevPedia-CocoaCore/Bundle.html>;
> for example applications are bundles. But that's not the usage of "bundle"
> that the error message refers to.
> Rather, it refers to one of the two different ways that shared libraries
> can be created on OS
> X<https://developer.apple.com/library/mac/#documentation/Porting/Conceptual/PortingUnix/compiling/compiling.html%23//apple_ref/doc/uid/TP40002850-SW5>.
> The most common way is by using the -dynamiclib flag, which creates a
> dynamic library that can be linked to. The other less-common way is by
> using the -bundle flag, which is for creating plugins that are loaded by
> an application at runtime. Shared libraries created with this flag cannot
> be linked to; that's what the error message is saying: you're trying to
> link to libociei.dylib as if it were a dynamic library, but for Instant
> Client 11 it appears that Oracle has compiled it as a plugin so that's not
> possible anymore.
So does this mean we just need a "-dynamiclib" flag added to our compiler
when Apple is detected? If so, where would I place this flag... :)
Everything else below this line is my trial and error, no need to read. :)
-Tres
--------------------------------------------------
Other random thoughts that will eventually be part of Google's archive of
search results... :)
This post on stackoverflow says it could be due to the linker:
http://stackoverflow.com/questions/20321600/how-to-link-compiled-object-file-hello-o-with-ld-on-mac-os-x
But i'm not optimistic about the solutions as I think linking is working
here, the compiler is just blocking it because it's a "bundle", whatever
that is :)
I'm finding several complaints about this... There seems to be 2 general
causes:
1. Building libraries with a compiler other than clang (I guess this could
be the case for Wine, but I don't see the connection, since libvstbase.so
doesn't directly link against wine. Do we define an explicit gcc compiler
for libvstbase.so? (I would assume not) If so, where can I switch it
back? :)
2. Or... The new behavior with Mavericks/XCode 5.1/clang in regards to
something apple calls library bundles versus dylibs. Not to be confused
with an application bundle (these names are confusing!) I still don't
really understand this though because the whole "dylib" versus "so" thing
hasn't caused any issues with the rest of the project...
Some related articles:
http://yorick.sourceforge.net/phpBB3/viewtopic.php?f=9&t=326
https://github.com/ryanmelt/qtbindings/issues/72
http://stackoverflow.com/questions/19630154/gem-install-therubyracer-v-0-10-2-on-osx-mavericks-not-installing
https://github.com/xbmc/xbmc/commit/444d5b661eb0537e4a30e57c78b6c327bf71e251
http://stackoverflow.com/questions/6655548/need-help-linking-to-bundle-on-os-x
https://github.com/SOCI/soci/issues/89
-Tres
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees_APR
_______________________________________________
LMMS-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmms-devel
