Does the pspec here use Winebuild? Sorry I can't check at the moment.
If it does, the current winebuild allows you to specify exports for a
given arch by passing
-arch=cpu
in the spec file.
On Tue, Feb 10, 2009 at 10:15 AM, <tkreuzer(a)svn.reactos.org> wrote:
> Author: tkreuzer
> Date: Tue Feb 10 09:15:07 2009
> New Revision: 39533
>
> URL: http://svn.reactos.org/svn/reactos?rev=39533&view=rev
> Log:
> x64 version of ntoskrnl doesn't export ExInterlockedAddLargeStatistic
>
> Modified:
> branches/ros-amd64-bringup/reactos/ntoskrnl/ntoskrnl.pspec
>
> Modified: branches/ros-amd64-bringup/reactos/ntoskrnl/ntoskrnl.pspec
> URL: http://svn.reactos.org/svn/reactos/branches/ros-amd64-bringup/reactos/ntosk…
> ==============================================================================
> --- branches/ros-amd64-bringup/reactos/ntoskrnl/ntoskrnl.pspec [iso-8859-1] (original)
> +++ branches/ros-amd64-bringup/reactos/ntoskrnl/ntoskrnl.pspec [iso-8859-1] Tue Feb 10 09:15:07 2009
> @@ -104,7 +104,9 @@
> @ stdcall ExInitializeRundownProtectionCacheAware(ptr long)
> @ stdcall ExInitializeZone(ptr long ptr long)
> @ stdcall ExInterlockedAddLargeInteger(ptr long long ptr)
> +#ifndef __x86_64__
> @ fastcall ExInterlockedAddLargeStatistic(ptr long)
> +#endif
> @ stdcall ExInterlockedAddUlong(ptr long ptr)
> #ifndef __x86_64__
> @ fastcall ExInterlockedCompareExchange64(ptr ptr ptr ptr)
>
>
--
Steven Edwards
"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo
Folks,
I don't know where to ask this question, So decided to ask it on Dev mailing
list.
I am new to ReactOS and installed it on VMWare workstation and really loved
it.
It's behavior look and feel is like Windows and I really appreciate it
(although there is long way to for it)
Few of my questions are below:--
1) Is there any development kit for developing applications for ReactOS?
2) If not, Will Applications developed using Windows SDK (not .net
framework and all, just plain SDK) will work on ReactOS?
3) If Apps developed on Windows works on ReactOS, Are libraries developed
for Windows (which just depend on kernel32, user32 and other system dlls)
will work on ReactOS?
I am planning to use ReactOS for one of my custom device (using x86 based
processor) and want to develop some applications on top of it.
Regards
Deepak
Hi,
I am currently having a small problem on the x64 branch, maybe someone
can help me.
In wdm.h there's the following declarations:
#if defined (_WIN64)
#if defined(_NTDRIVER_) || defined(_NTDDK) || defined(_NTIFS_) || \
defined(_NTHAL_) || defined(_NTOSP_)
NTKRNLAPI
USHORT
ExQueryDepthSList(IN PSLIST_HEADER Listhead);
#else
FORCEINLINE
USHORT
ExQueryDepthSList(IN PSLIST_HEADER Listhead)
{
return (USHORT)(ListHead->Alignment & 0xffff);
}
#endif
#else
#define ExQueryDepthSList(listhead) (listhead)->Depth
#endif
So when compiling ntoskrnl, ExQueryDepthSList is not inlined. Later in
wdm.h (currently in our winddk.h, but to be moved to wdm.h)
ExQueryDepthSList is used in ExFreeToNPagedLookasideList inline function.
But I want ExQueryDepthSList to be inlined from within ntoskrnl. The
question is how can I achieve this?
If I #define it to be inline in ntoskrnl's private headers, it will not
affect ExFreeToNPagedLookasideList.
When I declare it as an inline function after the header is included, I
get a warning that it was declared inline after being used and that a
static declaration follows a non-static. (Does anyone know hoe to
disable these stupid warnings?)
Declaring it inline before including wdm.h doesn't work, as the needed
declaration for SLIST_HEADER is missing.
Anyone got any other idea? I'd like to avoid hacking our public headers,
to keep them as compatible to ms headers as possible.
Regards,
Timo