You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by "Schreibman, David" <DS...@eTranslate.com> on 2001/11/06 19:29:48 UTC

RE: cvs commit: jakarta-tomcat-connectors/jk/native/isapi isapi.d sp

OK, I was starting to get a bit confused myself (not hard to do).  Now I
realize you were just checking the file in without actually using it -
right?

I'm not a real expert on the topic but have used Visual Studio enough to
know that the .dsw and .dsp files are generated by the GUI to define a
hierarchy between a "workspace" and a collection of "projects".  The .dsw
file can hold configuration information that is common to all of its
projects.  I've never really seen a case where anybody actually had more
than one project in a workspace - such as here with isapi.

In any case, the studio let's you export a make file which you can then use
as a starting point and then get rid of the .dsw and .dsp.  Although the
.dsp can be used for command line builds, I have worked on many projects
where we exported the make files from an initial project and then never
really worked in the studio again.  The generated make file is intended for
use by microsoft's nmake but is closer to a regular make file and does not
break your build just because you edit the file  (the .dsp is not friendly
about manual edits).

It definitely remains a platform specific build, but I think it's a step in
the right direction.

Back to your other questions:
	No, there are no hard-coded paths
	Yes, the Makefile yields the same build as the .dsw/.dsp - a dynamic
link library.

Check it out.  I just generated this one for you from the cvs head.

I sent in a similar example/patch for mod_jk a couple of weeks ago but I
think people were too busy with the 3.3 final and nobody got a chance to
take a look at it.

Hope this helps.

-David





> -----Original Message-----
> From: cmanolache@yahoo.com [mailto:cmanolache@yahoo.com]
> Sent: Monday, November 05, 2001 10:34 PM
> To: Tomcat Developers List
> Subject: RE: cvs commit: jakarta-tomcat-connectors/jk/native/isapi
> isapi.d sp
> 
> 
> On Mon, 5 Nov 2001, Schreibman, David wrote:
> 
> > Costin,
> >
> > Did you consider exporting the equivalent Makefile from the studio?
> 
> Hard to do on my Linux :-)
> 
> Is the generated makefile 'equivalent' with the DSP/DSW ? Is it
> usable on other machines or does it have hardcoded paths ?
> 
> ( I'm confused - so many projects are using dsp/dsw instead 
> of makefiles -
> it  should be a reason for doing that )
> 
> Costin
> 
> > >   I'm not sure what's the relation between .dsp files and
> > > .dsw, but it would be much easier if
> > >   we would use (n)makefiles and remove the binary .dsw.
> 
> 
> 
> 
> --
> To unsubscribe, e-mail:   
> <ma...@jakarta.apache.org>
> For additional commands, e-mail: 
> <ma...@jakarta.apache.org>
> 


RE: cvs commit: jakarta-tomcat-connectors/jk/native/isapi isapi.d sp

Posted by co...@covalent.net.
On Tue, 6 Nov 2001, Keith Wannamaker wrote:

> I hope nobody is proposing tossing the .dsp files.
> It sure is convenient to checkout the project and double
> click on a .dsp to load up all the dependencies in VS.
> Since the .dsw will be generated automatically from a .dsp,
> it is not needed in the repository, unless (like in the case
> of Apache) one wants to group ALL projects together.
>
> If you want to include the generated nmake .mak files,
> ok, (however it is easy for the .dsp and .mak to get
> out of sync).  But I'd be -1 regarding tossing the .dsp files.

If .dsp files are not 'equivalent' with .mak, then we should
keep the .dsp and not check in the .mak.

The problem was that we have to keep the .dsp file in sync with
the Makefiles for unix. The other problem is that we have 4-5
.dsp files - for each target.

Would it be possible to use some macros or to generate the .dsp file?

Costin









--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


RE: cvs commit: jakarta-tomcat-connectors/jk/native/isapi isapi.d sp

Posted by Keith Wannamaker <Ke...@Wannamaker.org>.
I hope nobody is proposing tossing the .dsp files.
It sure is convenient to checkout the project and double
click on a .dsp to load up all the dependencies in VS.
Since the .dsw will be generated automatically from a .dsp,
it is not needed in the repository, unless (like in the case
of Apache) one wants to group ALL projects together.

If you want to include the generated nmake .mak files,
ok, (however it is easy for the .dsp and .mak to get
out of sync).  But I'd be -1 regarding tossing the .dsp files.

Keith

| -----Original Message-----
| From: Schreibman, David [mailto:DSchreibman@eTranslate.com]
| Sent: Tuesday, November 06, 2001 1:30 PM
| To: 'Tomcat Developers List'
| Subject: RE: cvs commit: jakarta-tomcat-connectors/jk/native/isapi
| isapi.d sp
| 
| In any case, the studio let's you export a make file which you can then use
| as a starting point and then get rid of the .dsw and .dsp.  Although the
| .dsp can be used for command line builds, I have worked on many projects
| where we exported the make files from an initial project and then never
| really worked in the studio again.  The generated make file is intended for


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


RE: cvs commit: jakarta-tomcat-connectors/jk/native/isapi isapi.d sp

Posted by co...@covalent.net.
On Tue, 6 Nov 2001, Schreibman, David wrote:

> OK, I was starting to get a bit confused myself (not hard to do).  Now I
> realize you were just checking the file in without actually using it -
> right?

Yes, I'm using either Makefiles/configure or ant. The problem is that
anyone changing in one place must sync with the other build system.

> really worked in the studio again.  The generated make file is intended for
> use by microsoft's nmake but is closer to a regular make file and does not
> break your build just because you edit the file  (the .dsp is not friendly
> about manual edits).

Ok, that may be a problem - is there any way to edit .dsp without
breaking it ? I assume most people who use unix are doing it for some
reasons, so requiring everyone to run windows is a bad idea.

If you can't generate the .dsp file from .mak - then I think it's better
to keep only the .dsp, we already have a huge problem keeping the .dsp
in sync with the 'real' makefile.

> Check it out.  I just generated this one for you from the cvs head.

Thanks for the info and patch. But I agree with Keith, we can't remove
the .dsp and having yet another place to sync is not a good idea.

> I sent in a similar example/patch for mod_jk a couple of weeks ago but I
> think people were too busy with the 3.3 final and nobody got a chance to
> take a look at it.

Sorry about that.

Costin


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>