auto vs manual vc6 project files naming conflict

[Royce Mitchell III]

our "make -vs6 msvc" command generates dsp files automatically for all 
project in the tree.

At the moment, this is overwriting the following files:

subsys/system/explorer/notifyhook/notifyhook.dsp
    subsys/system/ibrowser/ibrowser/ibrowser.dsp
    lib/opengl32/opengl32.dsp
    lib/cpl/ncpa/ncpa.dsp
    lib/cpl/control/control.dsp
    lib/cpl/appwiz/appwiz.dsp

Would anybody have a problem with it if I renamed all these dsp files 
out of the way, or would it be better if the auto-generated dsp files 
were named something like notifyhook_auto.dsp?

Thanks

[Casper Hornstrup]

Why not just delete them?

Casper
> -----Original Message-----
> From: [e-mail] [mailto:[e-mail]] On Behalf Of Royce Mitchell
> III
> Sent: 2. november 2005 15:15
> To: ReactOS Development List
> Subject: [ros-dev] auto vs manual vc6 project files naming conflict
>
> our "make -vs6 msvc" command generates dsp files automatically for all
> project in the tree.
>
> At the moment, this is overwriting the following files:
> subsys/system/explorer/notifyhook/notifyhook.dsp
> subsys/system/ibrowser/ibrowser/ibrowser.dsp
> lib/opengl32/opengl32.dsp
> lib/cpl/ncpa/ncpa.dsp
> lib/cpl/control/control.dsp
> lib/cpl/appwiz/appwiz.dsp
>
> Would anybody have a problem with it if I renamed all these dsp files
> out of the way, or would it be better if the auto-generated dsp files
> were named something like notifyhook_auto.dsp?
>
> Thanks
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev

[Steven Edwards]

--- Casper Hornstrup [e-mail] wrote:
> Why not just delete them?

YES. Please remove the msvc files from the tree and just fix all the autogeneration.

Thanks
Steven

__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com

[Martin Fuchs]

Hi Royce,

2005/11/2, Royce Mitchell III [e-mail]:
> our "make -vs6 msvc" command generates dsp files automatically for all
> project in the tree.
>
> At the moment, this is overwriting the following files:
>
> subsys/system/explorer/notifyhook/notifyhook.dsp
>    subsys/system/ibrowser/ibrowser/ibrowser.dsp
>    lib/opengl32/opengl32.dsp
>    lib/cpl/ncpa/ncpa.dsp
>    lib/cpl/control/control.dsp
>    lib/cpl/appwiz/appwiz.dsp
>
> Would anybody have a problem with it if I renamed all these dsp files
> out of the way, or would it be better if the auto-generated dsp files
> were named something like notifyhook_auto.dsp?

2005/11/3, Steven Edwards [e-mail]:
> Why not just delete them?
>
> YES. Please remove the msvc files from the tree and just fix all the

autogeneration.

please don't remove the VC project files of Explorer, Winefile and
IBrowser. I am using them outside of the source tree, and they contain
information which is not (and will/can not) be autogenerated.

Regards,

Martin

[Royce Mitchell III]

Martin Fuchs wrote:
> Hi Royce,
>
> 2005/11/2, Royce Mitchell III [e-mail]:
> > our "make -vs6 msvc" command generates dsp files automatically for all
> > project in the tree.
> >
> > At the moment, this is overwriting the following files:
> >
> > subsys/system/explorer/notifyhook/notifyhook.dsp
> >   subsys/system/ibrowser/ibrowser/ibrowser.dsp
> >   lib/opengl32/opengl32.dsp
> >   lib/cpl/ncpa/ncpa.dsp
> >   lib/cpl/control/control.dsp
> >   lib/cpl/appwiz/appwiz.dsp
> >
> > Would anybody have a problem with it if I renamed all these dsp files
> > out of the way, or would it be better if the auto-generated dsp files
> > were named something like notifyhook_auto.dsp?
>
> 2005/11/3, Steven Edwards [e-mail]:
> > Why not just delete them?
> >
> > YES. Please remove the msvc files from the tree and just fix all the
>
> autogeneration.
>
> please don't remove the VC project files of Explorer, Winefile and
> IBrowser. I am using them outside of the source tree, and they contain
> information which is not (and will/can not) be autogenerated.
>
> Regards,
> Martin

I figured this was the case Martin. Is it okay if I rename your dsp 
files so they don't get in the way of the auto-generated ones, or would 
you prefer I modify the auto-generated ones to have _auto in the name?

[KJKHyperion]

Royce Mitchell III wrote:
> I figured this was the case Martin. Is it okay if I rename your dsp 
> files so they don't get in the way of the auto-generated ones, or 
> would you prefer I modify the auto-generated ones to have _auto in the 
> name?

use a suffix. It's likely that we will import third party projects which 
already have their own .dsp files

[Martin Fuchs]

2005/11/3, Royce Mitchell III [e-mail]:
> > please don't remove the VC project files of Explorer, Winefile and
> > IBrowser. I am using them outside of the source tree, and they contain
> > information which is not (and will/can not) be autogenerated.
> >
> > Regards,
> > Martin
>
> I figured this was the case Martin. Is it okay if I rename your dsp
> files so they don't get in the way of the auto-generated ones, or would
> you prefer I modify the auto-generated ones to have _auto in the name?

2005/11/3, KJKHyperion [e-mail]:
> use a suffix. It's likely that we will import third party projects which
> already have their own .dsp files

Yes, I think also naming the generated files in a unique way would be
the best solution.

Regards,

Martin

[Alex Ionescu]

Martin Fuchs wrote:
> Hi Royce,
>
> 2005/11/2, Royce Mitchell III [e-mail]:
> > our "make -vs6 msvc" command generates dsp files automatically for all
> > project in the tree.
> >
> > At the moment, this is overwriting the following files:
> >
> > subsys/system/explorer/notifyhook/notifyhook.dsp
> >   subsys/system/ibrowser/ibrowser/ibrowser.dsp
> >   lib/opengl32/opengl32.dsp
> >   lib/cpl/ncpa/ncpa.dsp
> >   lib/cpl/control/control.dsp
> >   lib/cpl/appwiz/appwiz.dsp
> >
> > Would anybody have a problem with it if I renamed all these dsp files
> > out of the way, or would it be better if the auto-generated dsp files
> > were named something like notifyhook_auto.dsp?
>
> 2005/11/3, Steven Edwards [e-mail]:
> > Why not just delete them?
> >
> > YES. Please remove the msvc files from the tree and just fix all the
>
> autogeneration.
>
> please don't remove the VC project files of Explorer, Winefile and
> IBrowser. I am using them outside of the source tree, and they contain
> information which is not (and will/can not) be autogenerated.
>
> Regards,
> Martin

You should just tell us what kind of information they contain so that we 
can update the XML file. It will be perfectly auto-generated afterwards.

Best regards,
Alex Ionescu

[Martin Fuchs]

2005/11/3, Alex Ionescu [e-mail]:
> You should just tell us what kind of information they contain so that we
> can update the XML file. It will be perfectly auto-generated afterwards.

Well, I don't doubt you would be able to to so. But I think the effort
to implement such all the required features into the XML files and
rbuild isn't worth it. I will show you what "information" I thought
of:

- In the Explorer workspace the source files are organized into a
handfull of subfolders, e.g. "utility", "resources", "taskbar", "doc",
...

- In the "doc" folder there are files which are not to be compiled -
text files like "changes.txt" merely for documentation purpouse.

- The work space contains more than one project file: Some in VC
internal format, some just calling external Makefiles - even a
Jamfile.

- The project file contains different configurations: Debug/Release
configurations, UNICODE/ANSI configurations. There is also a
configuration I am using to build Explorer together with Wine's
libraries, such as shell32.dll and comctl32.dll, and link to them
instead of Windows' DLLs.

- explorer.xml and the genersated ReactOS Makefiles define different
compiler options, like "-D_ROS_" and "-__WINDRES__", which my native
VC project files don't need.

Regards,

Martin