Path: ...!news.mixmin.net!proxad.net!feeder1-2.proxad.net!usenet-fr.net!.POSTED!not-for-mail From: Olivier Miakinen Newsgroups: fr.comp.lang.c Subject: Re: gcc/linux => mingw/windows/cygwin Date: Mon, 25 Nov 2024 23:12:47 +0100 Organization: There's no cabale Lines: 35 Message-ID: References: NNTP-Posting-Host: 200.89.28.93.rev.sfr.net Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 8bit X-Trace: cabale.usenet-fr.net 1732572768 2466 93.28.89.200 (25 Nov 2024 22:12:48 GMT) X-Complaints-To: abuse@usenet-fr.net NNTP-Posting-Date: Mon, 25 Nov 2024 22:12:48 +0000 (UTC) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.4 In-Reply-To: Bytes: 2073 Bonjour, Le 25/11/2024 15:37, JKB a écrit : > [...] > > U __imp_CyUartClearDtr > U __imp_CyUartClearRts > U __imp_CyUartSetDtr > U __imp_CyUartSetHwFlowControl > U __imp_CyUartSetRts Ça semble en effet être une microsofterie, apparemment liée à l'utilisation de bibliothèques de liens dynamiques (DLL). Par exemple je trouve ceci en faisant une recherche sur « prefix __imp_ » : The __imp__ prefix appears whenever you are linking to a DLL. It does not appear when linking to statically linked libraries. Most likely the code is generated to be linked against a DLL import lib, but you have linked it with a static lib instead. The prefix is added when you mark the imported function with __declspec(dllimport) - make sure your imports are not using this when not linking against a DLL. Voir peut-être aussi : -- Olivier Miakinen