Hi,
ok... last but not least, RosBE for Windows Version 2.0 is out too.
This is one of the last steps to the upcoming cmake switch with dumping rbuild fully and forever.
The setup files can be found here:
http://www.reactos.org/wiki/Build_Environment
Setup is the same good known NSIS based one for now. Just remove the old BE and let it install it over.
CMAKE usage instructions are here:http://reactos.org/wiki/CMake
Big thanks for this release goes to Heis and Colin from the Unix BE team, Amine for not killing me taking so long for a release and dralnix and blight_ for doing the first steps to a advanced BE years ago. Miss you, guys ^^
As for Unix one, I fully dump the support for any earlier Version of RosBE Windows starting from NOW.
Best regards,
Daniel
Hi,
finally, we are getting closer and closer to CMake switch. RosBE-2.0
release brings supports for CMake and all the changes made in the tool
chain. You can find it here:
https://sourceforge.net/projects/reactos/files/RosBE-Unix/2.0/
To install it, simply extract the tar.bz2, and then run the
RosBE-Builder.sh script.
For instructions about how to use CMake in ReactOS, have a look to that
wiki page: http://reactos.org/wiki/CMake
Regarding this release, I would like to thank Colin Finck who did
everything for it, but who have been obliged to let me release his work
due to his busy life.
RosBE 1.5 is not supported any longer.
And I invite everyone to switch to CMake (with RosBE2.0 Windows/Linux).
Rbuild deletion is now a matter of days.
The countdown for Rbuild deletion has started.
Regards,
Pierre
I must say, hpoussin proposed to get rid of bget in favor of rtl/heap.c,
and I criticized his idea because I had no trust in the old heap code.
Would reusing the new code be an option? Or you already invented the
"mini-heap" which works good enough?
WBR,
Aleksey.
On 10.02.2012 0:01, tkreuzer(a)svn.reactos.org wrote:
> Author: tkreuzer
> Date: Thu Feb 9 20:01:10 2012
> New Revision: 55518
>
> URL: http://svn.reactos.org/svn/reactos?rev=55518&view=rev
> Log:
> [FREELDR]
> - Enable new heap code and cleanup the heap, releasing unused memory, before starting reactos
> - Gives our kernel about 4MB additional memory, which - at the current leak rate - means around 8 minutes longer before it runs out of memory :)
> - Using the temp heap for all temporary allocations should increase the amount of saved space
>
> Removed:
> trunk/reactos/boot/freeldr/freeldr/mm/heap.c
> trunk/reactos/boot/freeldr/freeldr/rtl/bget.c
>
Hi all,
The Google Summer of Code 2012 project registration phase is starting in
three weeks.
Are we going to apply again after our success last year?
Who will be available as administrators and mentors?
Is anybody already collecting task ideas?
Cheers,
Colin
Le 06/02/2012 07:50, janderwald(a)svn.reactos.org a écrit :
>
> +if(ARCH MATCHES i386)
> + add_target_compile_flags(disk "-mrtd -fno-builtin -Wno-unused-variable -Wno-pointer-sign")
> +endif()
> +
>
Hey!
Those look very GCC centric. The corresponding flag for MSVC to -mrtd
would be /Gz. As for other flags, I'm unsure of what -fno-builtin would
correspond to, and others are only for warnings.
Cheers.
Jérôme.
Few changes you might find important:
- WDK builder has been added to scheduler. All trunk revisions are from now on built on both gcc and wdk.
- Cameron-requested USB builder is added as well. This one, connected to usb-bringup-trunk branch, is triggered manually from web interface. All builds are stored on diablo, so team-members with ftp accounts on it can access the builds just as all other ones. Please contact me if one needs an account.
Enjoy
--
With best regards
Caemyr
A second RC for 0.3.14 has been posted here:
http://sourceforge.net/projects/reactos/files/ReactOS/0.3.14/0.3.14-RC2.iso…
The main purpose of this RC is to see whether the hack Cameron Gutman
provided works around the memory manager issue causing hangs while
copying mshtml.dll during installation. Due to problems with the
wallpapers, a livecd will not be built at this time.
Z98
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
No, the Apache License isn't compatible with GPLv2, but it's
compatible with GPLv3
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJPKys0AAoJEOb7MMS0s1Vr6u0H/irIogS+rc59Q+8RUVS48OyA
6bPFeyGM//egEWmERvLOl4CBRe9DsPQiGhFzxOeo79khwA6lWhWD+bO5hOGuWpCZ
GaKD5Ejy5kXf3ksDBH39/taYRCJo5z84aKEujncvKBhWSMFEVKGOADVopV/X1v8y
bj9OrVJJzuUDZJw/uBkZFmbTLdGAPIAv/Z8+5qfsiUJnD/lWGN+9n+by/08shpG7
7fJW7OJu+z0j/VTxNwsP6cGlgLSOFONlMHrjBHLMd9wLqdN3FwnxOlkgwAch8lj+
XXVGcv5P1diubQt/Foy+clRYUWBL9xfbClBLU7+V+mdE6n3ssLYI7MZnbCR5LIw=
=4MHl
-----END PGP SIGNATURE-----
Hello,
we just had a monthly meeting in the beginning of January, so I don't
see much of a reason to do another one at our usual date (and there are
no urgent questions required for decision).
Next meeting is going to happen in the end of February as scheduled.
WBR,
Aleksey.