If there is nothing in hpiview, that is not provided by hpibrowser, and if there is nobody crying for support, we should abandon hpiview. I'll try to find hpiview2 also. Cheers, Uli
> -----Original Message----- > From: ext Anton Pak [mailto:[email protected]] > Sent: Wednesday, June 02, 2010 4:10 PM > To: [email protected] > Subject: Re: [Openhpi-devel] Installing hpiview > > We may if there is a man eager to support hpiview. > I also saw hpiview2 in svn repository. > Have no idea what is it. > > For differences: > Hpibrowser supports DIMI and FUMI and HPI-B.03 innovations. > > Anton Pak > > On Wed, 02 Jun 2010 17:56:36 +0400, Kleber, Ulrich (NSN - DE/Munich) > <[email protected]> wrote: > > > Hi, > > OK. I'll add something about pkgconfig in the README. > > Do you think we should support hpiview and hpibrowser in parallel? > > I just installed both of them, so I don't have a feeling about > > the differences. > > Cheers, > > Uli > > > >> -----Original Message----- > >> From: ext Anton Pak [mailto:[email protected]] > >> Sent: Wednesday, June 02, 2010 3:41 PM > >> To: [email protected] > >> Subject: Re: [Openhpi-devel] Installing hpiview > >> > >> Uli, > >> > >> There is no relation between hpiview and hpibrowser. > >> I recall hpiview had been abandoned before my entrance in OpenHPI. > >> Hpibrowser is just an another attempt to create GUI tool for HPI. > >> > >> I can share your pain about those auto-hell build tools. :) > >> There are always problems when one encounters these tools. > >> > >> Suggest to add some wordings about pkg-config along with your > >> changes into > >> hpiview README file. > >> What say? > >> > >> Anton Pak > >> > >> On Wed, 02 Jun 2010 17:24:25 +0400, Kleber, Ulrich (NSN - > DE/Munich) > >> <[email protected]> wrote: > >> > >> > Hi Anton, > >> > I am not sure I want to be maintainer for hpiview - > >> especially since I > >> > don't know > >> > yet about the relation of hpiview and hpibrowser. > >> > > >> > But I'll make a proposal for a new README file. > >> > > >> > > >> > For the pkg-config. I am a stupid user of these build > >> tools. Can't we > >> > add a statement > >> > somewhere, so the hpi installation path is automatically added to > >> > PKG_CONFIG_PATH, > >> > before the make install calls pkg-config? > >> > Probably that's just my stupid newcomer's thinking. > >> > > >> > Cheers, > >> > Uli > >> > > >> > > >> >> -----Original Message----- > >> >> From: ext Anton Pak [mailto:[email protected]] > >> >> Sent: Wednesday, June 02, 2010 3:23 PM > >> >> To: [email protected] > >> >> Subject: Re: [Openhpi-devel] Installing hpiview > >> >> > >> >> Uli, > >> >> > >> >> o) Well, there is no active hpiview maintainer. > >> >> You may take this responsibility and change README file. > >> >> > >> >> o) From man pkg-config: > >> >> > >> >> -------------------------- > >> >> By default, pkg-config looks in the directory > >> >> prefix/lib/pkgconfig for > >> >> these files; it will also look in the colon-separated > >> >> (on Windows, > >> >> semicolon-separated) list of directories specified by the > >> >> PKG_CONFIG_PATH environment variable. > >> >> -------------------------- > >> >> I think official packages in major Linux distributions take > >> >> care of this > >> >> issue. > >> >> You compiled openhpi from sources and had to deal with > >> >> pkg-config yourself. > >> >> > >> >> > >> >> Anton Pak > >> >> > >> >> > >> >> > >> >> On Wed, 02 Jun 2010 17:10:11 +0400, Kleber, Ulrich (NSN - > >> DE/Munich) > >> >> <[email protected]> wrote: > >> >> > >> >> > Hi, > >> >> > > >> >> > - README > >> >> > openhpi itself has a very nice README file. > >> >> > Maybe the hpiview README should be something similar. > >> >> > When I read that, the ./bootstrap shouldn't be > necessary when the > >> >> > released tarball is used. But I think I needed > ./bootstrap in all > >> >> > cases. > >> >> > Shall I try to propose a better README file? > >> >> > > >> >> > - pkgconfig > >> >> > I used the default /usr/local/lib. > >> >> > Shouldn't it work automatically there? > >> >> > > >> >> > Cheers, > >> >> > Uli > >> >> > > >> >> > > >> >> > > >> >> > > >> >> >> -----Original Message----- > >> >> >> From: ext Anton Pak [mailto:[email protected]] > >> >> >> Sent: Wednesday, June 02, 2010 12:51 PM > >> >> >> To: [email protected] > >> >> >> Subject: Re: [Openhpi-devel] Installing hpiview > >> >> >> > >> >> >> Uli, > >> >> >> > >> >> >> Have no idea about README. > >> >> >> What changed do you propose to make? > >> >> >> > >> >> >> By default pkg-config looks only in /usr/lib|lib64/pkgconfig. > >> >> >> If you installed openhpi with prefix other than /usr - > >> >> >> you have to come to an agreement with pkg-config. :) > >> >> >> > >> >> >> Anton Pak > >> >> >> > >> >> >> On Wed, 02 Jun 2010 14:38:33 +0400, Kleber, Ulrich (NSN - > >> >> DE/Munich) > >> >> >> <[email protected]> wrote: > >> >> >> > >> >> >> > Yes, it worked. Hpiview runs. > >> >> >> > Thanks, Anton! > >> >> >> > > >> >> >> > My only questions. > >> >> >> > - Should we change the README file? > >> >> >> > - Why did openhpi not correctly register when I installed > >> >> >> it? Did I do > >> >> >> > something wrong then? > >> >> >> > > >> >> >> > Cheers, > >> >> >> > Uli > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> >> -----Original Message----- > >> >> >> >> From: ext Anton Pak [mailto:[email protected]] > >> >> >> >> Sent: Wednesday, June 02, 2010 10:47 AM > >> >> >> >> To: [email protected] > >> >> >> >> Subject: Re: [Openhpi-devel] Installing hpiview > >> >> >> >> > >> >> >> >> Uli, > >> >> >> >> > >> >> >> >> Hope this screenshot helps. > >> >> >> >> > >> >> >> >> Anton Pak > >> >> >> >> > >> >> >> >> > >> >> >> >> On Wed, 02 Jun 2010 11:55:58 +0400, Kleber, Ulrich (NSN - > >> >> >> DE/Munich) > >> >> >> >> <[email protected]> wrote: > >> >> >> >> > >> >> >> >> > Hi, > >> >> >> >> > I am trying to install hpiview, after I got > openhpi 2.15.0 > >> >> >> >> running with > >> >> >> >> > multiple domains (on ATCA), and also run the new > >> hpibrowser. > >> >> >> >> > > >> >> >> >> > But I ran into a few problems. > >> >> >> >> > > >> >> >> >> > The README file says: > >> >> >> >> > > >> >> >> >> > To build hpiview do: > >> >> >> >> > make -f Makefile.dist > >> >> >> >> > ./configure > >> >> >> >> > make > >> >> >> >> > cd HpiView > >> >> >> >> > ./HpiView > >> >> >> >> > > >> >> >> >> > But there is no Makefile.dist. > >> >> >> >> > > >> >> >> >> > So I tried to run ./bootstrap instead. > >> >> >> >> > Then I started ./configure, but the dependency check > >> >> >> doesn't find my > >> >> >> >> > openhpi: > >> >> >> >> > > >> >> >> >> > checking for HPI... configure: error: Package > requirements > >> >> >> >> (openhpi >= > >> >> >> >> > 2.0.0) were not met: > >> >> >> >> > > >> >> >> >> > No package 'openhpi' found > >> >> >> >> > > >> >> >> >> > Consider adjusting the PKG_CONFIG_PATH environment > >> >> >> variable if you > >> >> >> >> > installed software in a non-standard prefix. > >> >> >> >> > > >> >> >> >> > Alternatively, you may set the environment variables > >> >> HPI_CFLAGS > >> >> >> >> > and HPI_LIBS to avoid the need to call pkg-config. > >> >> >> >> > See the pkg-config man page for more details. > >> >> >> >> > > >> >> >> >> > I am sorry, but I am still a bit new with that > build stuff, > >> >> >> >> so I was not > >> >> >> >> > able to do those adjustments. I installed the openhpi in > >> >> >> >> standard paths. > >> >> >> >> > > >> >> >> >> > Cheers, > >> >> >> >> > Uli > >> >> >> >> > >> >> >> > > >> >> >> > > >> >> >> > -------------------------------------------------------------- > >> >> >> ---------------- > >> >> >> > > >> >> >> > _______________________________________________ > >> >> >> > Openhpi-devel mailing list > >> >> >> > [email protected] > >> >> >> > https://lists.sourceforge.net/lists/listinfo/openhpi-devel > >> >> >> > >> >> >> > >> >> >> > -------------------------------------------------------------- > >> >> >> ---------------- > >> >> >> > >> >> >> _______________________________________________ > >> >> >> Openhpi-devel mailing list > >> >> >> [email protected] > >> >> >> https://lists.sourceforge.net/lists/listinfo/openhpi-devel > >> >> >> > >> >> > > >> >> > > >> >> -------------------------------------------------------------- > >> >> ---------------- > >> >> > > >> >> > _______________________________________________ > >> >> > Openhpi-devel mailing list > >> >> > [email protected] > >> >> > https://lists.sourceforge.net/lists/listinfo/openhpi-devel > >> >> > >> >> > >> >> -------------------------------------------------------------- > >> >> ---------------- > >> >> > >> >> _______________________________________________ > >> >> Openhpi-devel mailing list > >> >> [email protected] > >> >> https://lists.sourceforge.net/lists/listinfo/openhpi-devel > >> >> > >> > > >> > > >> -------------------------------------------------------------- > >> ---------------- > >> > > >> > _______________________________________________ > >> > Openhpi-devel mailing list > >> > [email protected] > >> > https://lists.sourceforge.net/lists/listinfo/openhpi-devel > >> > >> > >> -------------------------------------------------------------- > >> ---------------- > >> > >> _______________________________________________ > >> Openhpi-devel mailing list > >> [email protected] > >> https://lists.sourceforge.net/lists/listinfo/openhpi-devel > >> > > > > > -------------------------------------------------------------- > ---------------- > > > > _______________________________________________ > > Openhpi-devel mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/openhpi-devel > > > -------------------------------------------------------------- > ---------------- > > _______________________________________________ > Openhpi-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/openhpi-devel > ------------------------------------------------------------------------------ _______________________________________________ Openhpi-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openhpi-devel
