Home > Community > Forums > System Design and Verification > linking shared libraries

Share

  • Email
  • Social Web
* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

 linking shared libraries 

Last post Mon, Mar 31 2008 1:30 PM by admin. 0 replies.
Started by admin 31 Mar 2008 01:30 PM. Topic has 0 replies.
Page 1 of 1 (1 items)
Sort Posts:
  • Mon, Mar 31 2008 1:30 PM

    • admin
    • Top 25 Contributor
    • Joined on Thu, Feb 7 2008
    • San Jose, CA
    • Posts 167
    • Points 745
    linking shared libraries Reply

    Hello, I have developed a couple of shared libraries, CFC and VHPI, for C access to VHDL design and NCSIM simulator. I used Cadence recommended Pliwizard to compile the libraries. I get no errors while building the libraries. But when I dynamically link the libraries to my application using GNU linker I get undefined reference errors at every function call in both shared libraries. The shared libraries use Cadence provided vhpi_user.h and cfclib.h files which define various functions. These header files are included in the shared library sources. It seems that Pliwizard builds the shared libraries but does not properly link with other dependent sources. I am now poised to build the libraries with Makefile template which is hierarchal and definitely not a pretty option. Please share you experience of linking shared objects. Regards, Yaseen

    • Post Points: 5
Page 1 of 1 (1 items)
Sort Posts:
Started by admin at 31 Mar 2008 01:30 PM. Topic has 0 replies.