CMAKE does have a built-in feature to generate GraphViz (dot) dependency graphs
of a project. I am unsure why Timo wrote his own script to do so, but CMAKE can
definitely do it.
-r
> Am 31.12.2010 17:58, schrieb Ged Murphy:
> > I didn't know about this feature.
> > Will this help the effort tow
Hello,
Why everyone else had been complaining on how we should revert changes that
expose compiler bugs, I, on the other hand, have not even been able to build
ReactOS anymore starting with recent revisions (probably related to C++
changes).
Anyone want to fix this, please?
[PCH] obj-i38
Hello,
As some have asked,
http://www.youtube.com/watch?v=RFNuY2OFRjU&hd=1
Cheers!
-r
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
Hi,
Oops! Google Chrome could not connect to build.reactos.org:8010
It was a typo in my e-mail. I've used this website fine in the past before.
-r
> Hi
>
> Please try the correct address: http://build.reactos.org:8010/
>
> 2010/11/20 Ros Arm
>
> > Hi,
&
Hi,
It appears your arguments are because you don't seem to understand what you
have done wrong.
Let me spell it out:
" I know that r49463 only added INIT_FUNCTION to HAL, but I reverted both, just
to be sure. I can get back ntoskrnl as they don't seem to be concerned."
ie:
"I know that my f
Hi,
Considering that:
- The code to throw out INIT sections isn't in trunk, so _nothing happens_ when
a function is made INIT or not.
- There were already many INIT functions in NTOSKRNL and the kernel worked fine
- 49463 only added INIT_FUNCTION to the HAL
- A later revision by Timo added INIT_
http://img209.imageshack.us/img209/5379/stuff0.png
-r
> http://img824.imageshack.us/img824/734/stuffy.png
>
> -r
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
http://img824.imageshack.us/img824/734/stuffy.png
-r
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
Hello,
The jgardou changes add thousands of whitespace changes which make it extremely
hard to understand what is going on. Please to not arbitrarily change
whitespace across 18 files in a patch!
Also, there is nothing wrong with the way ClassPNP was defined before. If you
think "How on Earth
for it to remain a PE file (and I don't think
> easier debugging is a good reason), I would like to see the PE changes to
> FreeLoader reverted.
>
> -Original Message-
> From: ros-dev-boun...@reactos.org [mailto:ros-dev-boun...@reactos.org] On
> Behalf Of Ros Arm
> Ros Arm wrote:
> > Hello,
> >
> > After the switch in 48124 to PE FreeLDR, I am unable to boot FreeLDR any
> > longer.
> >
> > I have tried official, as well as various unofficial freeldr.sys, none
> > worked.
> >
> > 47892 version works
Unknown, this FIXME was copy/pasted from other .rbuild files which already
contained similar hacks.
Note: adding oldnames library does not fix the issue.
-r
> sir_rich...@svn.reactos.org wrote:
> > Author: sir_richard
> > Date: Mon Sep 20 06:30:21 2010
> > New Revision: 48825
> >
> >
> > +
>
I believe it was communicated to my team we are shooting for win2003, not 2008,
which is an entirely different kernel architecture (Vista/Win7).
You should use a more appropriate driver, or file a bug with the driver
developer.
-r
> I don't think this has anything to do with amount of memory.
Hello,
After the switch in 48124 to PE FreeLDR, I am unable to boot FreeLDR any longer.
I have tried official, as well as various unofficial freeldr.sys, none worked.
47892 version works fine, 48124 does not.
On a 512MB IDE disk, I got the "_" VGA cursor scrolling endlessly/randomly on
the scr
Hello,
eVb checked in one of his final patches yesterday from his development machine
in China, where we worked on a final pass on the driver. Unfortunately, my last
two (unrelated) check ins were done from his machine (as most of you know, I
was in China for the past month), and he was not use
Hello,
Many thanks for fixing this idiotic oversight of mine. I apologies for the long
hours of debugging I must have caused.
This fix is somewhat incomplete/at the wrong place; could this be marked as
such in the code, perhaps with a FIXME under my name, so that I may fix this
correctly upon
Hello,
A recent CMAKE commit has made me notice that a NOSWPAT option determines if
FreeType hinting should be used or not. Please note that the Apple patent on
the technology recently expired, and this option is not needed anymore, as
hinting should always be enabled.
-r
Hello,
Thank you Cameron (47516). +1!
Carry on!
-r
> Hello,
>
> First I was asked if a certain developer could talk to me regarding ARM3. I
> said yes, never heard back, and then saw commits done to pfnlist.c. While
> interesting and useful code, some communication would've been nice in orde
Hello,
First I was asked if a certain developer could talk to me regarding ARM3. I
said yes, never heard back, and then saw commits done to pfnlist.c. While
interesting and useful code, some communication would've been nice in order to
talk about the goals, since much of that code is in flux (I
Hello!
While the state of the original code is horrendous, and removing it was a step
in the good direction, this simplified implementation omits many of the
optimizations and specific VGA tricks that the original "author" of the code
had intended to duplicate.
If you'd like, I would be open t
Hello,
This is the second time that work that someone on the ARM Team has worked on
has been mostly reverted without any communication with us, and incorrect
changes have been added to parts of our work.
The Eng function worked on even clearly stated comments such as "Compressed
surfaces don't
Good evening,
Even past EngCreateBitmap fix in trunk, VGA driver I wrote still having many
problems drawing, most with text output and colors. Example, desktop icon
appear monochrome, not color. But Paint palette has 16 colors. When draw in
Paint, white background become black! And after releas
I had told the channel not to do this because HAL ACPI does not exist yet. ACPI
cannot work without it, other than by random chance or coincidence.
-r
> Very nasty.
>
> --
> From:
> Sent: Wednesday, March 17, 2010 8:02 AM
> To:
> Subject: [ros-d
Hello Steven,
I have talked with eVb and perhaps there is a language barrier:
His commit message said that he used the NT4 DDK driver because the license
does not prohibit it (especially as only a fraction of it is used).
He then said that there have been some small number of changes since NT4,
Stipulation only exist in newer DDK, that why old sample used.
Also, storage drivers in ReactOS are NT4 (atapi) DDK sample too, so why raising
issue now?
[eVb]
> Does the EULA allow you to redistribute sample code without
> stipulations? I seem to recall certain versions of the DDK requiring
>
Hi Jose,
I think there are some misunderstandings regarding the GCC code base I would
like to clear up inline.
> Hi,
>
> Don't feel offended, the port to c is a very good thing and indeed better in
> the most part than the previous asm implementation. I value your work very
> much.
> But there
Hello,
Would you care to comment on "unefficient" regarding the trap rewrite, please?
The code is more efficient than previous assembly code, and more finely tuned
than Windows' own code, which wasn't updated since 1989 when it was first
designed (and is full of non-pairing, hazardous operation
> > Since __builtin_unreachable is only for GCC 4.5, we use
> > exit(0) for now (it will never be reached) to trick GCC.
>
> There is also __builtin_trap() …
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/
Hi Timo,
Regarding #1, we actually have this working in our tree. It was required for
the new SYSENTRY C handler. So thank you for the advice and for pointing that
out. Unfortunately I will not credit you for the idea since the code was
already written, I hope this is understandable. We had to
obably more complicated than that).
So to close the topic: it is unclear if you have any ownership of those
original 6 lines of code, and it is even further unclear if 6 lines of
interface code in a 466 line module allow you the right to dictate the license
of the module.
-r
> Ros Arm wro
years ago, it
makes sense this code is now belong to us.
It is Linux concept of "maintainer".
Thanks you,
[eVb]
> "You may relicense my code as BSD" != "You make strip away
> copyright/ownership of my code".
>
> Revert this.
>
&
Hello,
I have identified a major deficiency in the x86 kernel that requires minor
overhaul of multiple low-level components, and stems from poorly understood
implementation details of the x86 architecture, which is NMI support.
NMIs are Non Maskable Interrupts, similar to SMIs (generated for SM
Dear ReactOS Members,
We'd like to issue you our warmest holiday greetings and a happy new year!
Withal, receive our cordial gratitude for the recent work on getting the ARM
tree building again as well as for extending support for Windows and Mac OS X
build systems throughout this troubled time
33 matches
Mail list logo
