Databases
StackOverflow2013
Postsdbo
POCreating and using dynamic libraries in OS X
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCreating and using dynamic libraries in OS X
    primarykey
    data
    text
    <p>We have a Windows application written in C++, part of which we are trying to port to Mac OS X. Our goal is to wrap the business logic into some libraries and build a Cocoa layer on top for the controller and the GUI. We will probably have several smaller apps using the same libraries so our first thought was to use dynamic libraries for the C++ code (unless there is a better way). However, we are having some problems with achieving this. Our dynamic library complies fine (at least it looks like that) and we get a .dylib file which we link to in our app. The problem is that our app simply can't find any of the .h files we are trying to include. We have already checked that the .h files are being exported as well as checked the install name and made sure that the library is located in the correct directory. Also, we have followed Apple's guide for creating and using dynamic libraries and found no special step we were missing.</p> <p>My question here is in two parts:</p> <ol> <li>Is there some obvious step we might be missing which is instrumental in exposing the interface (i.e. the .h files) that we should try before anything else?</li> <li>We do suspect that the fault might be in the crappy C++ code we have inherited in this project. For instance, there is a lot of logic (implementation of methods) written directly in .h files and in some cases there isn't even a corresponding .cpp file at all. So the .h files aren't merely a description of the interface. This might not be the (solemn) problem as our app can't even find the .h files from the library and they should at be least present. We really hope that we can avoid rewriting a lot of the code since the code base which needs to be ported is really large and (as usual) the deadline is close.</li> </ol> <p>PS: We have so far only been working in Xcode 4.2 and have not tried with the command line tools yet.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USpajevic
    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. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POCreating and using dynamic libraries in OS X
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POCreating and using dynamic libraries in OS X
      1. This table or related slice is empty.
      1. VTUpMod
    1. COMake sure you’ve specified the path to your library’s include files in your project/target’s build settings: Header Search Paths or User Header Search Paths.
      singulars
      1. POCreating and using dynamic libraries in OS X
      1. This table or related slice is empty.
    2. COMake sure that the header files are where you expect them to be (in the filesystem)
      singulars
      1. POCreating and using dynamic libraries in OS X
      1. USarne
    3. COWe have actually done this out of pure desperation and it sort of worked. But is this really necessary? I mean, that means that when you distribute the library you have to distribute the header files as well. So the .dylib does not work in a similar way as a .dll file in Windows which is completely self contained?
      singulars
      1. POCreating and using dynamic libraries in OS X
      1. USpajevic
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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