Ok thanks, any way I install react os tools and now I using ninja.
It's good. Thanks for the help!
2015-08-09 23:27 GMT+02:00 David Quintana (gigaherz) :
> #reactos-dev requires asking permission to speak, as a means to avoid
> spam. You can ask on #reactos, or you can send a private message to
>
#reactos-dev requires asking permission to speak, as a means to avoid
spam. You can ask on #reactos, or you can send a private message to
someone.
On 9 August 2015 at 18:48, Alberto Vaudagna wrote:
> Hi, I join the reactOs dev chat #ReactOS-Dev but when I try to send a
> message the client (I'm u
Thanks - I'll take a look at the suggested bits of code. Incidentally I did try
to get into C++ development and object-oriented design a while ago, but found
that I get a lot more done in C (there are other things I now prefer about C
but it's pointless for me to go into them here ;) )
I'm not
Hi, I join the reactOs dev chat #ReactOS-Dev but when I try to send a
message the client (I'm using the web interface webchat.freenode.net) give
me an error saying I cannot send the message. Do I need to be verify my
account against the reactos account?
Any way If I run the configure without param
For COM classes in the context of ReactOS, I'd recomment the existing
code in Shell components. for declaring and using COM classes from C,
there's code coming from WINE that could serve as an example, and for
proper COM done with C++, we have examples of both ATL-based COM such
as the rshell modul
Hi Andrew,
that's very nice to hear from you and we all are pretty much excited
here at the ReactOS Hackfest in Aachen that you are interested in audio
development again!
If you have a possibility - grab a ticket from London and come straight
away here, as the Hackfest lasts till 13th.
I hop
I knew I should have left out number 3. I really don't care what label we use,
the other two arguments are what matters.
On August 9, 2015 3:33:13 PM CEST, "David Quintana (gigaherz)"
wrote:
>I say this as a joke, but it also happens to be a perfectly valid
>argument in favour of the change: Ca
Hi everyone,
Some of you probably remember me. I was involved with trying to get
audio/sound implemented in ReactOS a few years ago.
To be honest, my progress was rather poor, I managed to write a few bits of
code but never really had a proper understanding of kernel/OS development or
CPU/s
I say this as a joke, but it also happens to be a perfectly valid
argument in favour of the change: Calling it "recycle bin" promotes
recycling, which is a good practice that the project should support,
and well, you ARE recycling those HDD sectors for later use... ;P
On 9 August 2015 at 12:32, Hu
Trash is an American term, while recycling is universal amongst English
speakers. In Australia we say garbage (not trash) for actual waste and
recycling for recyclables.
On Sun, Aug 9, 2015 at 7:46 PM, Thomas Faber
wrote:
> Well... since you asked...
> Really good reason not to: if something's
Well... since you asked...
Really good reason not to: if something's not broken, don't fix it.
Really good reason not to: if everything works fine and the user experience is
generally Windows-like, we should NOT try to make things more Windows-like. On
the contrary. Different is good, both in ter
Hello.
I propose to change the structure of the HAL.
i.e. to build different hal's (hal.dll, halacpi.dll etc not from different libs
(generic, acpi, apic, up, legacy etc.),
and using constructs like #ifdef _ACPI_HAL_.
For example, generic/dma.c in the acpi version need when entering sleep mode
12 matches
Mail list logo
