Hi,
we're stright aproaching a new release.
Or at first: A branch.
What about the version number? As far as I followed the discussions, 0.3
is still away :-( .
And how about our new build system. Is it successfully running?
I for my part would feel more comfortable if the next
intermediate-release would still use the old build system.
`Remove two file that are not need any longer
fix some compilings warings' <==
--- Ge van Geldorp <gvg(a)reactos.com> a écrit:
> > From: greatlrd(a)svn.reactos.com
> >
> > Updated files:
> > trunk/reactos/lib/cabinet/cabextract.c
> > trunk/reactos/lib/cabinet/cabinet_main.c
>
> What's the purpose of the changes you made to these two files?
>
> Gé van Geldorp.
>
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.com
> http://reactos.com:8080/mailman/listinfo/ros-dev
>
Kind regards,
Usurp (aka Sylvain Petreolle)
humans are like computers,
yesterday the BIOS was all
- today its just a word
> From: greatlrd(a)svn.reactos.com
>
> Updated files:
> trunk/reactos/lib/cabinet/cabextract.c
> trunk/reactos/lib/cabinet/cabinet_main.c
What's the purpose of the changes you made to these two files?
Gé van Geldorp.
Hi,
Here is my beef with rbuild. I can't fix most of these as I don't have
the skills/knowledge of rbuild.
1) Project link flags are applied at the end of the command line...this
makes -Wl optimization flags not work.
2) DBG = 0 and GCC 4 creates a load of new warnings that weren't there
before. For example, I can't build ntoskrnl anymore. This is because
it's detecting "uninitialized variables" which are actually being
initalized by the macros themselves (see mm/pe.c and elf.inc.h). This
did not happen before rbuild.
3) Strip isn't being executed for dbg = 0 anymore... I can add it but I
have no idea how to make it dbg = 0 only.
Not sure:
4) Is the OPTIMIZED envirovar still taken into account? I didn't seem to
see so.
Best regards,
Alex Ionescu
Hi.
I believe the new build system is ready to replace the current build system in trunk. Unless there are objections, I plan on merging
the branch to trunk in the weekend of 27 - 29 of may.
I'd like to take the opportunity to thank everyone that helped make this possible - especially Royce Mitchell III, Ge van Geldorp,
and Steven Edwards.
It would be nice if you could checkout the branch and check that the features you can't live without are still there so we can have
them ready before the merge. If you have major new feature requests that are not essential, I'd like to put them on hold until after
the merge. To checkout the branch do a:
svn co svn://svn.reactos.com/branches/xmlbuildsystem/reactos
For a list of environment variables that controls the build see:
http://svn.reactos.com/viewcvs/*checkout*/branches/xmlbuildsystem/reactos/M…
For more technical information see:
http://svn.reactos.com/viewcvs/*checkout*/branches/xmlbuildsystem/reactos/t…
This is not a 100% solution to our dependency problems though. There can still be corner-cases where it is needed to manually clean
some files, but it will be needed a lot less than today. Also in order to have acceptable performance, we cannot check dependencies
on every included file on each make invocation. Therefore, this is currently only checked each time the automatically generated
makefile (makefile.auto) is regenerated. Makefile.auto is regenerated each time a build system file (*.xml) is modified. If you need
to check the dependencies on files not specified in the build system files "automatic dependencies", then delete makefile.auto and
run make again.
Casper
navaraf(a)svn.reactos.com wrote:
>Use W32API.
>
>
>Updated files:
>trunk/reactos/drivers/net/npf/Makefile
>trunk/reactos/drivers/net/npf/dump.c
>trunk/reactos/drivers/net/npf/jitter.c
>trunk/reactos/drivers/net/npf/openclos.c
>trunk/reactos/drivers/net/npf/packet.c
>trunk/reactos/drivers/net/npf/packet.h
>trunk/reactos/drivers/net/npf/read.c
>trunk/reactos/drivers/net/npf/win_bpf.h
>trunk/reactos/drivers/net/npf/write.c
>
>_______________________________________________
>Ros-svn mailing list
>Ros-svn(a)reactos.com
>http://reactos.com:8080/mailman/listinfo/ros-svn
>
>
>
This breaks the dbg=0 build because of the ASSERT macro in winddk.h.
Best regards,
Alex Ionescu
navaraf(a)svn.reactos.com wrote:
>Bye, bye "include/net/" directory...
>
>
>Deleted files:
>trunk/reactos/include/net/
>
>_______________________________________________
>Ros-svn mailing list
>Ros-svn(a)reactos.com
>http://reactos.com:8080/mailman/listinfo/ros-svn
>
>
>
This breaks the build because lib/packet can't find the net include
files anymore.
Best regards,
Alex Ionescu
greatlrd(a)svn.reactos.com wrote:
> VBE driver never write which reslutions it should use as defualt
> therefor the change resultions did not working on bootcd
> do not remove this settings. from the reg.
> Thanks
>
> >
> Updated files:
> trunk/reactos/bootdata/hivesys.inf
>
This is already possible in the "hiveinst.file"
It should be only in one place
Regards
Gge
--- Robert K�pferl <rob(a)koepferl.de> wrote:
> we're stright aproaching a new release.
> Or at first: A branch.
> What about the version number? As far as I followed the discussions, 0.3
> is still away :-( .
>
> And how about our new build system. Is it successfully running?
> I for my part would feel more comfortable if the next
> intermediate-release would still use the old build system.
I would rather wait till Casper merges rbuild and we get it stable then tag a release. There is no
point in stablising the tree to just break it again in another week or two.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new Resources site
http://smallbusiness.yahoo.com/resources/