I like it, I would actually propose creating: kernel32.dll kernel32_vista.dll kernel32_win7.dll etc...
instead of just "kernelsup" What is important to me is that kernel32.dll remains 2003 kernel32.dll Best regards, Alex Ionescu On Sun, Mar 17, 2013 at 4:49 PM, Aleksey Bragin <[email protected]> wrote: > On 17.03.2013 20:25, Timo Kreuzer wrote: >> >> We can avoid that by organizing our code in static libraries and merge >> them all together to 2 core dlls. >> The division like on Windows 7: kernelbase + kernel32 + advapi32, doesn't >> work for us, since kernel32 and advapi32 would still need to contain Vista+ >> APIs. >> Therefore I suggest to divide it into kernelbase.dll and kernelsup.dll, >> the latter containing the code that remains in kernel32 and advapi32 on >> Windows. > > I like that. > > It would be interesting to listen to Alex's opinion on this matter. > > Regards, > Aleksey Bragin > > > _______________________________________________ > Ros-dev mailing list > [email protected] > http://www.reactos.org/mailman/listinfo/ros-dev _______________________________________________ Ros-dev mailing list [email protected] http://www.reactos.org/mailman/listinfo/ros-dev
