You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by "C. Michael Pilato" <cm...@collab.net> on 2004/04/07 21:54:34 UTC
Windows __INSTALLER__ MSVC project.
Could someone perhaps explain why we have an __INSTALLER__ project in
our Windows build that does nothing but call out to an installer.bat
which doesn't even exist? Am I supposed to provide that script?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Windows __INSTALLER__ MSVC project.
Posted by Branko Čibej <br...@xbc.nu>.
C. Michael Pilato wrote:
>Branko Čibej <br...@xbc.nu> writes:
>
>
>
>>C. Michael Pilato wrote:
>>
>>
>>
>>>Could someone perhaps explain why we have an __INSTALLER__ project in
>>>our Windows build that does nothing but call out to an installer.bat
>>>which doesn't even exist? Am I supposed to provide that script?
>>>
>>>
>>>
>>>
>>No. The installer project has to go.
>>
>>
>
>Could we instead make it do something sensible, like assemble the
>targets into a heirarchy:
>
> Release/bin
> Release/lib
> Release/lib/svn-python/libsvn
> Release/lib/svn-python/svn
> ...
>
>Purty please?
>
>
It doesn't make sense to have a .dsp target do that. It _does_ make
sense to have a python script. Again, I've been lazy in converting my
bash script to something committable.
--
Brane Čibej <br...@xbc.nu> http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Windows __INSTALLER__ MSVC project.
Posted by "C. Michael Pilato" <cm...@collab.net>.
Branko Čibej <br...@xbc.nu> writes:
> C. Michael Pilato wrote:
>
> >Could someone perhaps explain why we have an __INSTALLER__ project in
> >our Windows build that does nothing but call out to an installer.bat
> >which doesn't even exist? Am I supposed to provide that script?
> >
> >
> No. The installer project has to go.
Could we instead make it do something sensible, like assemble the
targets into a heirarchy:
Release/bin
Release/lib
Release/lib/svn-python/libsvn
Release/lib/svn-python/svn
...
Purty please?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Windows __INSTALLER__ MSVC project.
Posted by Branko Čibej <br...@xbc.nu>.
C. Michael Pilato wrote:
>Could someone perhaps explain why we have an __INSTALLER__ project in
>our Windows build that does nothing but call out to an installer.bat
>which doesn't even exist? Am I supposed to provide that script?
>
>
No. The installer project has to go.
--
Brane Čibej <br...@xbc.nu> http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org