Hi Gav,
May I ask that you do not reply to my previous e-mail on this subject.
Regards,
Tom
Macro __WINESRC__ is defined for dlls/wininet/cookie.c in the Makefile.
The file cookie.c includes wine/debug.h.
wine/debug.h includes windef.h.
windef.h defines the macro FAR to __ONLY_IN_WINELIB()
__ONLY_IN_WINELIB() defines to do_not_use_this_in_wine if __WINESRC__
The file dlls/wininet/cookie.c
I hope this is the right list for this.
Version 20031118
redhat 9
After running ./tools/wineinstall everything goes ok until i get the
following:
.
.
.
.
make[2]: Leaving directory
`/home/pbarclay/downloads/wine-20031118/dlls/mshtml'
make[2]: Entering directory
`/home/pbarclay/downloads/wine-20
On November 22, 2003 12:32 pm, Ferenc Wagner wrote:
> Thanks for the detailed explanations; I never use implicit
> rules (prefer static patters).
Same here, but Alexandre prefers them. Why is that Alexandre?
> I didn't want to bother with this until we decide on the
> interface. I don't know wha
Hi,
Are you the same guy who does maintains the ODBC driver for Postgresql?
Shachar
Hiroshi Inoue wrote:
--
Shachar Shemesh
Open Source integration & consulting
Home page & resume - http://www.shemesh.biz/
> 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
> BTW, there's no need to make the script bash specific,
> we can use expr instead:
>
> -i=$(($i+1))
> +i=`expr $i + 1`
That isn't a bashism, it is required to be supported by any shell
that claims to be Posix compliant.
That probably means everything except an AT&T/SYSV bourne shell.
If
"Dimitrie O. Paun" <[EMAIL PROTECTED]> writes:
> For unknown reasons, for msvcrt I get this:
> const char* subtests_for_test5[] = {
> "cpp^M",
> "file^M",
> "heap^M",
> "scanf^M",
> };
Oh, silly me, I forgot that I already noticed this problem
and get rid of it by putting
sed '1,/
On November 22, 2003 11:45 am, Dimitrie O. Paun wrote:
> Yes, there was a problem. For unknown reasons, for msvcrt
> I get this:
> const char* subtests_for_test5[] = {
> "cpp^M",
> "file^M",
> "heap^M",
> "scanf^M",
> };
Here is the fix for this one (to maketests):
- win
On November 22, 2003 11:07 am, Ferenc Wagner wrote:
> Btw, if it's you who ran the program
> under Wine, you may be interested in the results:
Speaking of which, I find the program too quite. I wasn't
sure (until I got your email) that it ran at all! We should
print the name of the currently runn
On November 22, 2003 11:07 am, Ferenc Wagner wrote:
>Hi Dimi,
>
> I appreciate your support very much. Now it's just a quick
> reflection on the patch you sent, before I can take a closer
> look and testing. Btw, if it's you who ran the program
> under Wine, you may be interested
Hi Dimi,
I appreciate your support very much. Now it's just a quick
reflection on the patch you sent, before I can take a closer
look and testing. Btw, if it's you who ran the program
under Wine, you may be interested in the results:
Tests from build Sat Nov 22 03:29:11 EST 2003
On November 21, 2003 12:16 pm, Ferenc Wagner wrote:
> I would be grateful for a review.
OK,
One more time, this round with a patch incorporating
most of my suggestions. What it does:
-- better integration in the build system
-- supports out of tree builds
-- cleans up file when winetests
Dimitrie O. Paun wrote:
Alexandre,
After this patch (provided you have applied the MCI one), you
should remove documentation/samples/system.ini:
$ cvs rm -f documentation/samples/system.ini
ChangeLog
Move the system.ini/[drivers32] section to the registry.
This will break any native Win9x
Dimitrie O. Paun wrote:
On September 23, 2003 02:47 pm, Eric Pouech wrote:
didn't search hard enough
in fact, I was searching in Win9x, where it isn't present, and only
configured in .ini files.
In NT, they seem to be stored in
for win.ini in
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\MCI E
Dimitrie O. Paun wrote:
Eric,
I think these values (*.drv) sit under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\MCI
and not under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\MCI32
as you suggested.
On NT, MCI key is for 16 bit drivers and MCI32 key
"Oleg Prokhorov" <[EMAIL PROTECTED]> wrote:
> Btw: What's the difference about {Global, Local, Virtual} memory
> allocation functions prefixes ? I didn't find any reasonable answer
> within MSDN
Global* and Local* API groups are the legacy APIs inherited from
16-bit Windows. In Win32 Local* APIs
18 matches
Mail list logo
