Simon Large wrote:
> Bill Hughes wrote:
>> smorf @ ihug wrote:
>>
>>>> Well, using MSBuild isn't a real option right now, because that
>>>> requires VS.NET2005 (or is it available for download??).
>>>
>>> Here is a link to where you can download .net 2.0 SDK
>>>
>>> http://lab.msdn.microsoft.com/vs2005/downloads/netframework/de
>>> fault.aspx
>>>
>>> It has everything you need to do development (compilers,
>>> documentation...). there are 'express' editions (free IDE, targeted
>>> at hobbyists) but I am unsure if you can get a C/++ express edition
>>
>>
>> That would be
>> http://lab.msdn.microsoft.com/express/visualc/
>
> Does that contain enough to build TSVN?
No, it doesn't include the MFC which is required.
> The build.txt file says that you need VS.NET, but the full VS.NET is
> quite expensive to buy. It would be very useful if we could
> pin down a
> minimal set of compiler/SDK tools, (preferably free :-) )
> which can be
> used to build TSVN.
I agree but it doesn't seem likely.
I have the Visual C++ 2003 Toolkit which is/was free and the Platform SDK
which is/was also free - I can't find the downloads any more. The vs2005
express components are apparently going to be $49 (which I still won't be
able to buy at work).
I also have gcc/cygwin (not sure why Stefan doesn't like cygwin but never
mind).
I can't build TSVN :-(
If you want to re-write TSVN to work without MFC you can have lots of fun
:-)
I'd prefer not to need visual studio but that is in no way a criticism or
objection to Stefan's technical decisions, just disappointment that I can't
join in (if my c++ ever got good enough).
Bill
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
*** Confidentiality Notice *** Proprietary/Confidential
Information belonging to CGI Group Inc. and its affiliates
may be contained in this message. If you are not a recipient
indicated or intended in this message (or responsible for
delivery of this message to such person), or you think for
any reason that this message may have been addressed to you
in error, you may not use or copy or deliver this message
to anyone else. In such case, you should destroy this
message and are asked to notify the sender by reply email.
Received on Fri Jul 29 11:54:38 2005