Re: [AMOS-devel] AMOS release *Update*

[Michael S. <ms...@um...>]

Thanks for the update Dan -  I look forward to the official release. Perhaps
in the future we could tag versions as pre-release or official versions.

The 'bankviewer' directory contains the published version of hawkeye, using
Qt version 3 going back to my original work some 6 years ago. 'hawkeye'
contains a new experimental version based on Qt version 4 created using the
qt 3 to 4 conversion tool and a lot of manual work. The Qt4 version is
mostly working, but some aspects remain broken from the Qt conversion
(mostly cosmetic problems).

In the short term, the Qt3 version is more stable, but it is becoming
increasingly difficult to install Qt3. In the long term, the Qt4 based
version is where the development effort needs to go. I don't have any
resources to work on hawkeye for at least the next several months, so it is
not included in the default build but is included in the tarballs for users
that only have qt4 available.

Best,

Mike




On Thu, Dec 9, 2010 at 5:05 PM, Daniel Sommer <ds...@um...>wrote:

> Hi Florent,   Thanks for you feedback on the issues below.  I agree that we
> should have done a better job keeping everyone updated on the status of the
> release as its been in limbo for over 1 month due to various issues.  The
> tarball has been released because some users needed it but not officially
> announced as I was updating the website before I sent out an email to
> everyone.  I will try address your questions below and next time I
> definitely welcome any help reviewing new releases before they are put up on
> the server.
>
> Dan
>
> PS.  Using amo...@li... in the future is a good idea
> and all developers should be on it.
>
>
> On Thu, Dec 9, 2010 at 1:59 AM, Florent Angly <flo...@gm...>wrote:
>
>>
>>
>> 2/ The AMOS version number was not updated for this release. It should be
>> changed to 3.0.0 in the file configure.ac
>>
>
> This is now updated.
>
>
>>
>>
>>  4/ I still get warnings when installing AMOS. I can try to fix them, but
>> before I do, does anyone know already exactly how to fix them?
>> Deprecated warnings:
>> In file included from
>> /usr/lib/gcc/x86_64-redhat-linux/4.4.5/../../../../include/c++/4.4.5/ext/hash_map:60,
>>                 from ../../../src/AMOS/utility_AMOS.hh:38,
>>                 from ../../../src/AMOS/foundation_AMOS.hh:13,
>>                 from clk.cc:15:
>> /usr/lib/gcc/x86_64-redhat-linux/4.4.5/../../../../include/c++/4.4.5/backward/backward_warning.h:28:2:
>> warning: #warning This file includes at least one deprecated or antiquated
>> header which may be removed without further notice at a future date. Please
>> use a non-deprecated interface with equivalent functionality instead. For a
>> listing of replacement headers and interfaces, consult the file
>> backward_warning.h. To disable this warning use -Wno-deprecated.
>>
>
>
> This is because <ext/hash_map> is not part of the standard C++ library and
> should be changed to include <unorder_map>  instead.  This shouldn't be a
> problem though and is a warning.  I didn't change this in the release as I
> am not sure of all the effects this could have on the core AMOS libraries
> (bugs, performance, etc).
>
>
>
>>
>> 5/ I've noticed that there are 2 apparently redundant folders in the main
>> CVS repository: 'bankviewer' and 'hawkeye'. Shall we remove one or the
>> other?
>>
>
>
> Not sure about this.  This would be up to the hawkeye developers.  You may
> want to ask Mike Schatz about this.
>
>
>>
>> 6/ I'd like to test some of the new features of AMOS. Yet, even as a
>> developer, I am unsure where to find them. For example, where is fast2amos
>> or goBambus2?
>>
>
>
> This will be updated in the latest tarball.  I am moving them to the
> Pipeline directory and Todd & I are updating the website documentation on
> them.
>
>
>
>>
>> 7/ At some point, Figaro was supposed to be integrated into the main AMOS
>> repository. This has not yet been done, and I'll probably do it myself
>> unless there are reasons not to.am
>>
>
>
> I don't think there is a reason not to do this.  I sent an email separately
> to you and James White about it.
>
>
>
>>
>> 8/ Recently, there were some emails on the mailing list from Martin
>> Mokrejs (mmo...@fo...). He reported many issues related to
>> compiling, but got very little feedback from us. Hopefully, we can address
>> some of his points so that he didn't feel like he entirely wasted his time
>> trying to help the AMOS project.
>>
>
> I believe I helped him get AMOS installed and running.  After he removed
> his old Bambus install and did a clean install of AMOS all of his
> compilation errors went away.  He had one warning remaining that is still
> outstanding.
>
>>
>>>
>
>>
>