Can't figure out where the rpm set things up

I've just followed the RPM install instructions and it looks as though everything went into place properly; as a note, I am using a freshly installed and updated fedora 9 build.

A "yum search mpf" tells me that things were installed, but from the "building your first component" guide I am told to go to my "mpf-work-dir," and I have no idea where that might be.  I'll keep looking, as maybe I am just overlooking it, but direction would help.

-Luke

Categories:

Missing install for mpf-core-devel

The install guide is missing a step to "yum install mpf-core-devel", which will be required once you actually try to build any mpf components. It includes the header files and the pkgconfig files for mpf.

    Adam

 

Re: Missing install instruction for mpf-core-devel

Hi Adam,

Thank you for catching this.  We'll get the Install Guide updated and re-posted.

-Maggie

 

 

Re: Can't figure out where the rpm set things up

Hi Luke,

The 'mpf-work-dir' refers to a directory you create which is where you will create components.  This would likely be a directory in your home folder.  For example,

mkdir /home/<username>/my-mpf-working-directory

cd /home/<username>/my-mpf-working-directory

./new-component.sh <your-component-name>

Do you think the instructions would be more useful if spelled out as above versus specifying 'mpf-work-dir'?  Thoughts?

-Maggie

Well, when I first looked at

Well, when I first looked at it, I assumed that was the case;  however the "./new-component.sh" command would refer to a script in the directory I just created, wouldn't it?  How does that get there?

-Luke

Sorry for the delay

Sorry for the lack of response, I have been ill. I will be looking into this today.

-Luke

mpf-new-component.sh

Hi Luke,

You can obtain the script mpf-new-component.sh by visiting the Download section of this site. Do the following:

  • Download the file mpf-new-component.txt and then rename it to mpf-new-component.sh. 
  • Copy the mpf-new-component.sh file to /usr/local/bin and make sure when it is written that it has execute permissions.
  • You should also verify that mpf-core is installed.  To do this, you can execute the following in the Terminal:

yum list mpf*

Give us an update here in the forums if you need further assistance.

-Maggie

Further difficulties

 

It seems like I'm not getting the packages properly

Here is my command history:

[luke@appscio ~]$ sudo wget http://www.appscio.com/repository/packages/continuous/trunk/fedora/9/RPM... -O /etc/yum.repos.d/appscio.repo
--2009-04-22 15:45:48--  http://www.appscio.com/repository/packages/continuous/trunk/fedora/9/RPM...
Resolving www.appscio.com... 75.101.165.134
Connecting to www.appscio.com|75.101.165.134|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 147 [text/plain]
Saving to: `/etc/yum.repos.d/appscio.repo'

100%[===============================================================================================>] 147         --.-K/s   in 0s      

2009-04-22 15:45:48 (8.23 MB/s) - `/etc/yum.repos.d/appscio.repo' saved [147/147]

[luke@appscio ~]$ sudo rpm --import http://www.appscio.com/repository/public_key
[luke@appscio ~]$ sudo yum install mpf*
Loaded plugins: refresh-packagekit
Setting up Install Process
Parsing package install arguments
No package mpf-test available.
Nothing to do
[luke@appscio ~]$ gst-inspect | grep mpf

(gst-inspect-0.10:5362): GLib-GObject-WARNING **: class finalizer specified for static type `MpfComponentTemplate_mpf-sfv-decode'

(gst-inspect-0.10:5362): GStreamer-CRITICAL **: gst_element_register: assertion `g_type_is_a (type, GST_TYPE_ELEMENT)' failed

(gst-inspect-0.10:5362): GLib-GObject-WARNING **: cannot register existing type `MpfComponent'

(gst-inspect-0.10:5362): GLib-GObject-CRITICAL **: g_type_register_static: assertion `parent_type > 0' failed

(gst-inspect-0.10:5362): GStreamer-CRITICAL **: gst_element_register: assertion `g_type_is_a (type, GST_TYPE_ELEMENT)' failed
mpf-opencv-opticalflow:  mpf-opencv-opticalflow: mpf-opencv-opticalflow
mpf-rdf-dump:  mpf-rdf-dump: mpf-rdf-dump
mpf-rdf-roimarkup:  mpf-rdf-roimarkup: mpf-rdf-roimarkup
mpf-opencv-haar:  mpf-opencv-haar: mpf-opencv-haar
mpf-ams-librarysink:  mpf-ams-librarysink: mpf-ams-librarysink
mpf-rdf-ton3:  mpf-rdf-ton3: mpf-rdf-ton3
[luke@appscio ~]$ yum list mpf*
Loaded plugins: refresh-packagekit
Error: No matching Packages to list
[luke@appscio ~]$

That should be all the steps from the guide.  Any clue what I am doing wrong?

-Luke

Re: Further difficulties

Hi Luke,

Sorry again that we are not getting back to you as quickly as we'd like.  In a week or so we will have wrapped up he product release that we're working on and will be able to spend more time on MPF support.

Could you run the following commands, and paste the output as a reply, to verify your installation ?

sudo cat /etc/yum.repos.d/appscio.repo (should print the contents of the appscio repo file)

sudo rpm -qi gpg-pubkey-* | grep appscio (should print one line of output: "Summary     : gpg(Appscio, Inc. (Appscio software) <support@appscio.com>)"

sudo yum list installed | grep mpf-

Once I see the output from these, I should be able to get you going again.

Thanks

Gareth

Output from commands

[luke@appscio ~]$ sudo cat /etc/yum.repos.d/appscio.repo
[sudo] password for luke:
# appscio.repo
#
 
[appscio]
name=Appscio
baseurl=http://www.appscio.com/repository/packages/continuous/trunk/fedora/9/RPMS/
enabled=1
gpgcheck=0

[luke@appscio ~]$ sudo rpm -qi gpg-pubkey-* | grep appscio
Summary     : gpg(Appscio, Inc. (Appscio software) <support@appscio.com>)
Summary     : gpg(Appscio, Inc. (Appscio software) <support@appscio.com>)
Summary     : gpg(Appscio, Inc. (Appscio software) <support@appscio.com>)
[luke@appscio ~]$ sudo yum list installed | grep mpf-
mpf-ams-librarysink.i386                  0.0.1.0-snapshot.r586.fc9    installed
mpf-ams-librarysink-debuginfo.i386        0.0.1.0-snapshot.r586.fc9    installed
mpf-core.i386                             0.0.3.1-snapshot.r634.fc9    installed
mpf-core-debuginfo.i386                   0.0.3.1-snapshot.r634.fc9    installed
mpf-core-devel.i386                       0.0.3.1-snapshot.r634.fc9    installed
mpf-iplimage.i386                         0.0.3.1-snapshot.r634.fc9    installed
mpf-iplimage-debuginfo.i386               0.0.3.1-snapshot.r634.fc9    installed
mpf-iplimage-devel.i386                   0.0.3.1-snapshot.r634.fc9    installed
mpf-opencv-opticalflow.i386               0.0.3.0-snapshot.r584.fc9    installed
mpf-opencv-opticalflow-debuginfo.i386     0.0.3.0-snapshot.r584.fc9    installed
mpf-rdf.i386                              0.0.1.0-snapshot.r585.fc9    installed
mpf-rdf-debuginfo.i386                    0.0.1.0-snapshot.r585.fc9    installed
mpf-rdf-devel.i386                        0.0.1.0-snapshot.r585.fc9    installed
mpf-rdftest.i386                          0.0.3.0-snapshot.r584.fc9    installed
mpf-rdftest-debuginfo.i386                0.0.3.0-snapshot.r584.fc9    installed
mpf-selectfocusvideo.i386                 0.0.1.0-snapshot.r628.fc9    installed
mpf-selectfocusvideo-debuginfo.i386       0.0.1.0-snapshot.r628.fc9    installed
[luke@appscio ~]$

Hope that helps -Luke

re: Output from commands

Thanks - it looks as if you have all the expected packages installed.

As we've been looking through the MPF documentation, we've found a few things that need to be added or clarified, which are likely to trip you up.  Normally we'd be able to look into these and give you a quick turnaround, but unfortunately, until we get our product release done nobody here has enough time to spend on it to give you an adequate response.  

We'll be back in touch around the middle of next week; thanks for your patience.

Gareth

checking in

Is everything going okay?  Sorry to be impatient, but I'd really like to get moving on this--Our other development really could use the system to be working.

 

-Luke

(Update) Re: checking in

G'day Luke,

Just wanted to update you regarding the Appscio MPF installation process.  We haven't been building for Fedora 9, 32-bit for a time and that contributed to the issues you were experiencing last week.  So, I've a couple of options for you to consider going forward:

  • Use the appscio.repo file and the newly attached Install Guide and Development Guide to do the RPM install of Appscio MPF on a Fedora 10, 64-bit server or virtual machine.  There are instructions in the Install Guide on how to proceed with this option.
  • If you want to continue using Fedora 9, 32-bit, you might consider doing a SVN checkout from https://svn.appscio.com/svn/MPF/trunk/ and then follow the './configure', 'make', 'make install' process.

I've tested both of the above options and am able to get Appscio MPF installed and up and running.  If you prefer, we could also make source RPMs available.  Please let us know which option is easiest for you.

-Maggie

To minimize confusion and

To minimize confusion and make my environment as close to yours as possible, I think we will want to go with the Fedora 10, 64 bit install.  I will probably need a couple of days to acquire a suitable machine for this and get it up and running.

Thanks,

Luke

Can you folks reccomend a

Can you folks reccomend a laptop to run the system on?  I would like to have hardware as similar to yours as possible.

Thanks,

Luke

Re: Can you folks recommend a...

Hi Luke,

Well, in my testing to date, I've been using a Mac Book Pro and creating virtual machines (e.g. VMWare) to create Fedora 10 testing environments.  I've also created virtual machine test environments on a desktop machine.  I would think that any laptop that has been recently manufactured should do the trick.

If you decide to go the VMWare (or other VM software, such as Virtual Box) route, I've been able to work with Appscio MPF using a minimal configuration of 1 processor, 768MB memory, and 50GB of disk.  I go a little high on the disk just as a personal preference and you can likely get by with less.

Let us know what you decide to use.

-Maggie