★ wanayoo — archive 1999 http://linux.ics.com/faqs/linking.htmlNouvelle recherche | Portail wanayoo

The Industry's Leading GUI Builder. Now for Linux!


Home
Product Information
Press Reviews
System Requirements
FAQ's
Documentation
Downloads
Support Center
About ICS

 

  1. I am porting code developed with BX Pro. The problem I am having is linking the EPak library to my code. During build I received the follwing "undefined references" to: ´ XmbufChangeWindowAttributes ´
    ´ XmbufCreateBuffers ´
    ´ XmbufDisplayBuffers ´
    ´ XmbufDestroyBuffers´
    ´ XmbufQueryExtension´
    ´ XmbufDestroyBuffers´
    ´ XmbufQueryExtension´
    Has anyone experienced this problem linking to the EPak libraries? How do you solve it?

    Answer:
    You are missing the X extensions library. Your compiler/linker line should look something like... gcc -o myapp ..... -lEPak -lXm -lXt -lSM -lICE -lXp -lXext -lX11 -lXmu –lm

  2. I am running Red Hat 6.0+ and using MetroLink Motif. I am having problems statically linking my software. What am I doing wrong?

    Answer:
    This is a known problem and MetroLink is offering a fix for registered users. Go to: http://www.metrolink.com/ for details and a workaround using dynamic linking.

  3. When I try to link my application, I am getting the following unresolved references:
    _XmDrawShadowType
    _XmManagerHelp ..etc.

    Answer:
    If you get unresolved references to Xm routines, (especially those that start with an underscore) it is likely because:
    1) you are using ViewKit or EnhancementPak and
    2) you are trying to use lesstif.
    ViewKit uses several internal Motif 1.2.x functions. These are not available in the current version of lesstif. The solution is to purchase Motif or not use ViewKit and/or EnhancementPak.

  4. I found the missing references mentioned in the question above in the latest release of lesstif. All I had to do was remove the modifier "static" and I was able to link and run! Is everything OK?

    Answer:
    No! Even if all the missing routines are available (perhaps under a slightly different scoping definition) they are not the same routines. For example, memory is not allocated the same between the real Motif versions of these routines and the ones provided by lessitf. This means that sooner or later your application will fetch, store, or jump to the wrong location and it will probably not terminate gracefully.


Other FAQs:
About| Install| Using| Integration| Linking| Widgets