From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=0.6 required=5.0 tests=BAYES_00,FROM_WORDY autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,1e18e59d68dcb061 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news3.google.com!news.glorb.com!news2.arglkargh.de!noris.net!news1.nefonline.de!not-for-mail From: "Alexander Camek" Newsgroups: comp.lang.ada Subject: Re: Undefined reference to glib_E Date: Mon, 26 Mar 2007 15:43:27 +0200 Organization: NEFkom - Mnet Telekommunikations GmbH Message-ID: References: <20070326151427.296f7b0e@cube.tz.axivion.com> NNTP-Posting-Host: pleione.3soft.de X-Trace: news1.nefonline.de 1174916572 13420 212.114.211.8 (26 Mar 2007 13:42:52 GMT) X-Complaints-To: usenet@news1.nefonline.de NNTP-Posting-Date: Mon, 26 Mar 2007 13:42:52 +0000 (UTC) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.3028 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-RFC2646: Format=Flowed; Original X-NNTP-Posting-Host: 10.1.1.39 Xref: g2news1.google.com comp.lang.ada:14641 Date: 2007-03-26T15:43:27+02:00 List-Id: "Stefan Bellon" schrieb im Newsbeitrag news:20070326151427.296f7b0e@cube.tz.axivion.com... > Alexander Camek wrote: > >> with "common"; >> with "framework"; >> >> project images is >> for Library_Name use "images"; >> for Library_Dir use "lib"; >> for Object_Dir use "obj"; >> for Library_Kind use "dynamic"; >> for Source_Dirs use (".", "bind"); >> for Languages use ("Ada", "C"); >> for Library_Interface use >> ("base_images", "generic_images", "images"); >> >> package Linker renames Common.Linker; >> package Compiler renames Common.Compiler; >> package Builder renames Common.Builder; >> package Ide renames Common.Ide; >> >> end images; >> >> When I do a static linking, everything works fine, but the dynamic >> linkage has this undefined reference. > > You are building a DLL on Windows here. A DLL cannot (unlike a > shared object on UNIX) have unresolved symbols. In the worst case you > need an import library. But in this case, there's another way. Okay, after some searching i found in the executable i build before the symbol :(. So it seems i have to use an import library, because it seems that the build will not work like under unix. I first build under unix my "executable" and then use many shared objects. Do I need in that case the previous named "import library", because windows is doing the whole a little bit diffrent? Thanks for the help Greetings Alexander