On Mon, 2004-01-05 at 13:04, Dimitrie O. Paun wrote:
> > There is at least one difference in using a wrapper & dll vs.
> > using a single executable: The function GetModuleFileName
> > doesn't yield the path to the program (the wrapper) with the
> > wrapper-approach (there was some discussion on th
The directory in which libwine.so.1 lives, is contained in my
/etc/ld.so.conf. Are you saying this should be enough for gcc
to find the library file?
In the other Makefile (the one where I invoke winebuild
explicitly), the path is passed (as an -L option) to
winebuild and g++ (c.f. variable LDFLAGS).
Ralf
--
Ralf Juengling <[EMAIL PROTECTED]>
Hi Dimi,
On Wed, 2003-12-31 at 16:47, Dimitrie O. Paun wrote:
> On December 31, 2003 07:42 pm, Ralf Juengling wrote:
> > okay, now it's as before:
>
> As I said, I think there's something wrong with your
> ld setup. You need to have /usr/local/lib (where
> the l
On Tue, December 23 2003 08:51 am, Dimitrie O. Paun wrote:
> On December 23, 2003 09:03 am, Vincent Béron wrote:
> > Not really. The problem in that case is that winemaker thinks every
> > resource file needs to be compiled independantly, when there's really
> > only one to compile in that case (as
- Original Message -
From: "Eric Pouech" <[EMAIL PROTECTED]>
To: "Ralf Juengling" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, December 23, 2003 11:05 PM
Subject: Re: GetModuleFileName mysteries
> basically, because for buil
ication name given to wine by the wineapploader script is
"phaeaco.exe" or "phaeaco.exe.so".
This is a confusing picture. Could somebody point out what the
expected result of GetModuleFileName is for this scenario (the
full path to the dll, I guess) and how it comes about that it
yields a path "C:\WINDOWS\SYSTEM\..."?
I observed this with Wine-20031118, haven't tested more recent
versions.
Ralf
--
Ralf Juengling <[EMAIL PROTECTED]>
> I have successfully compiled sources of a Windows application, but
> when starting up, it tries to locate and link to a windows dll
> to access some C library functions:
>
> ...
> err:module:import_dll No implementation for cw3230.DLL._strlen imported
> from L"Z:\\local\\builts\\phaeaco-2003111
> I have successfully compiled sources of a Windows application, but
> when starting up, it tries to locate and link to a windows dll
> to access some C library functions:
>
> ...
> err:module:import_dll No implementation for cw3230.DLL._strlen imported
> from L"Z:\\local\\builts\\phaeaco-2003111
fference.
I hope somebody can introduce me to secrets of simultaneously linking
against Winelib & Unix dynamic libraries..
Ralf
--
Ralf Juengling <[EMAIL PROTECTED]>
On Thu, 2003-11-20 at 11:21, Alexandre Julliard wrote:
> Ralf Juengling <[EMAIL PROTECTED]> writes:
>
> > Why doesn't it also add
> > /whereever/include/wine/msvcrt ?
>
> Because not everybody wants to use msvcrt. Unless you need some
> specific features o
Thanks.
On Thu, 2003-11-20 at 11:21, Alexandre Julliard wrote:
> Ralf Juengling <[EMAIL PROTECTED]> writes:
>
> > Why doesn't it also add
> > /whereever/include/wine/msvcrt ?
>
> Because not everybody wants to use msvcrt. Unless you need some
> specific fe
A Makefile created by winemake & configure adds
/whereever/include/wine/windows to the include paths.
Why doesn't it also add
/whereever/include/wine/msvcrt ?
What is the status of the include files in msvcrt?
Ralf
--
Ralf Juengling <[EMAIL PROTECTED]>
__WINE_LIMITS_H
#define INT_MAX 2147483647
-#define INT_MIN (-2147483648)
+#define INT_MIN (-INT_MAX-1)
#define SHRT_MAX 32767
#define SHRT_MIN (-32768)
--
Ralf Juengling <[EMAIL PROTECTED]>
wonder whether something is wrong with my Wine
installation or whether the test drive application simply
doesn't work in the current Wine release (wine-20031016).
Could somebody please confirm one or the other (winemine
compiles and runs with wine-20031016 or not)?
Thanks,
Ralf
--
Ra
ze (to the browser window).
Thanks,
Ralf
--
Ralf Juengling <[EMAIL PROTECTED]>
lib? Since I have no root account, I had to skip the invocation
of /sbin/ldconfig when installing wine-20031016. So I set
LD_LIBRARY_PATH to /local/lib:/local/lib/wine.
Any help appreciated,
Ralf
On Mon, 2003-10-27 at 18:23, Ralf Juengling wrote:
> On Mon, 2003-10-27 at 13:09, Alexandre Jullia
On Thu, 2003-10-30 at 08:58, Vincent Béron wrote:
> Le mer 29/10/2003 à 17:52, Ralf Juengling a écrit :
> > I was not successful with compiling the winemine application in
> > wine-20031016. When the resource compiler is to compile one
> > of the language dependent files, it
s
LANGUAGE LANG_ENGLISH, SUBLANG_ENGLISH_US
So it looks like wrc does not know what to do with the
constant LANG_ENGLISH. Is this a bug? Any idea whats going
wrong here?
Ralf
--
Ralf Juengling <[EMAIL PROTECTED]>
On Mon, 2003-10-27 at 13:09, Alexandre Julliard wrote:
> Ralf Juengling <[EMAIL PROTECTED]> writes:
>
> > So there is nothing I can do about it at the moment?
> > What is the most recent Wine version in which winemaker used to work?
>
> The previous release
> > checking for -lwine_uuid... /local/lib
> > checking for libntdll.dll.so... configure: error: Could not find the
> > Wine dlls (libntdll.dll.so)
> >
> Have you added /local/lib to /etc/ld.so.conf? If not, there should be a
warning when you install wine.
no, but I've set LD_LIBRARY_PATH to /loca
wine_unicode.so... /local/lib
checking for -lwine_unicode... /local/lib
checking for libwine_uuid.a... /local/lib
checking for -lwine_uuid... /local/lib
checking for libntdll.dll.so... configure: error: Could not find the
Wine dlls (libntdll.dll.so)
--
Ralf Juengling <[EMAIL PROTECTED]>
21 matches
Mail list logo
