Thanks for clarification
I received same mail from italian people with problem passing from
harbour beta to cvs
This can be resolved if viktor made periodical build


2009/8/20 Viktor Szakáts <harbour...@syenar.hu>:
>> Can you made easy for user of ViKtor's binary distro recompile from cvs
>> One single command update all bynary in harbour tree for all compiler
>> Platform / installed)
>
> That's not possible to do in a reasonable way.
>
> It's dead easy to do however (by looking into simple examples
> in INSTALL) if someone is aware of what tools she has installed
> on her system. Of course one can write a batch file which
> will blindly try to build Harbour for every possible targets,
> but that's not very professional-looking solution, so I don't
> plan to add anything like that.
A mingw version will be sufficent (32,64,ce)

>
> I think current default Harbour state cannot be any more simple,
> setting up tools and launching 'make' will remain the job of the
> builder.
>
>> Writing one/multiple  batch for recompile during install
>
> I don't plan to add any new batch/script file to our SVN,
> the goal is/was to get rid of them. Batch/script files reduce
> portability.
>
> Brgds,
> Viktor
>
>>
>> 2009/8/19  <vszak...@users.sourceforge.net>:
>>>
>>> Revision: 12185
>>>
>>> http://harbour-project.svn.sourceforge.net/harbour-project/?rev=12185&view=rev
>>> Author:   vszakats
>>> Date:     2009-08-19 17:49:51 +0000 (Wed, 19 Aug 2009)
>>>
>>> Log Message:
>>> -----------
>>> 2009-08-19 19:45 UTC+0200 Viktor Szakats (harbour.01 syenar.hu)
>>>  * utils/hbmk2/hbmk2.prg
>>>   + Added support for detecting Harbour binary environment
>>>     in raw form, meaning the one after simple 'make' *without*
>>>     'make install'.
>>>     Of course 'install' is still useful to build dlls (and
>>>     implibs on win), but for normal cases this may be a very
>>>     useful feature. You do a 'make' (no admin needed on *nix),
>>>     go to ./bin/arch/comp and hbmk2 works without any extra
>>>     configuration.
>>>     This feature also allows us to distribute multihost
>>>     binary packages. Such unified binaries can be run under
>>>     multiple hosts. (IOW we can have one binary distro which
>>>     covers potentially all our supported platforms/compilers
>>>     both as host OS and target OS). See watcom for such an
>>>     example in the C compiler world.
>>>
>>> Modified Paths:
>>> --------------
>>>   trunk/harbour/ChangeLog
>>>   trunk/harbour/utils/hbmk2/hbmk2.prg
>>>
>>>
>>> This was sent by the SourceForge.net collaborative development platform,
>>> the world's largest Open Source development site.
>>> _______________________________________________
>>> Harbour mailing list
>>> Harbour@harbour-project.org
>>> http://lists.harbour-project.org/mailman/listinfo/harbour
>>>
>>
>>
>>
>> --
>> Massimo Belgrano
>> _______________________________________________
>> Harbour mailing list
>> Harbour@harbour-project.org
>> http://lists.harbour-project.org/mailman/listinfo/harbour
>
> _______________________________________________
> Harbour mailing list
> Harbour@harbour-project.org
> http://lists.harbour-project.org/mailman/listinfo/harbour
>



-- 
Massimo Belgrano
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to