Tyler,
Thanks very much for the replies and suggestions. Your susicpions were
good, the path somehow included another version of the libtoolize and
this is what caused the error.
That said, I found some other heartaches, such as the configure script
not putting the proper prefix path in the GST_BASE_CFLAGS,
GST_BASE_LIBS, GST_CFLAGS, and GST_LIBS definition of the top level
makefile and src/makefile
They seemed to default to the system include directories, and lined in
libs from the system. This gave warnings but built, fooling me initially
into thinking all was well, but the gst-inpect would not recognize my
installed plugin
After I corrected those defines by hand, it would build, install, and
gst-inspect worked.
Sorry for the verbosity, but I wanted to state all I had to do to get
the process of gst-template to cross compile and be recognized by the DM355.
Anyway, thanks again for the pointers.
Mike
Tyler Nielsen wrote:
Mike,
When I cross compile, I run autogen.sh. As you pointed out, this
configures it for the current system. Then I run the configure for
the cross build. I'm sure there is a better way (like putting it into
the autogen script. I haven't worried about it too much because I run
it so rarely.
Looking at the messages you are getting, it looks like you may be
getting the two systems mixed. One gives an error from the
montavista, the other an error from /usr/share. I'm not sure if thats
a problem or not, but you may try running "/usr/bin/libtoolize --copy
--force" and see if that fixes the problem. From what I've seen, the
automake portion doesn't affect the cross compile. Just the configure
and make.
Tyler
On Tue, Apr 22, 2008 at 1:18 PM, Mike Patton <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Tyler,
thanks for your reply.
I have tried that, with the following results.
Mule ~/gstreamer/gst-template/test $ libtoolize --copy --force
libtoolize:
`/opt/mv_pro_4.0.1/montavista/common/bin/../share/aclocal-1.8/libtool.m4'
is serial 47, less than 52 in `aclocal.m4'
To remain compatible, you should update your `aclocal.m4' by
running aclocal.
Mule ~/gstreamer/gst-template/test $ aclocal
/usr/share/aclocal/nspr.m4:8: warning: underquoted definition of
AM_PATH_NSPR
/usr/share/aclocal/nspr.m4:8: run info '(automake)Extending aclocal'
/usr/share/aclocal/nspr.m4:8: or see
http://sources.redhat.com/automake/automake.html#Extending-aclocal
Then I tried configure, and it bombed with the same libtool.m4 /
ltmain.sh sanity check error
I'm sure I'm doing something wrong, just not sure what.
When starting from the scratch gst-template, I modify the
autogen.sh to reflect a single source file that exists in the src
dir, gstplugin.c
I verify that the src/Makefile.am also refers only to that file. I
looked through the configure.ac <http://configure.ac>, but it
doesn't seem to contain anything specific to source files, so I
left it alone.
Same error.
But I'm sure I'm missing a critical step(s), since I want to cross
compile, and that autogen wants to call configure. When I call
configure in the TI_build directories, I must prefix the command
with the cross compiler I want, such as:
CC=arm_v5t_le-gcc ./configure --build=i686-linux --host=arm-linux
--prefix=/DM355/filesys/opt/gstreamer
CFLAGS=-I"/DM355/filesys/usr/include
-I/DM355/filesys/opt/gstreamer/include/xdais"
LIBS=-L"/DM355/filesys/opt/system_files_gstreamer"
Seems like I should be adding a line to the autogen script or
similar to tell it to use this cross compiler.
That said, I thought that worst case, I just would get a plugin
built for the x86 instead of cross compiled for my ARM, but
instead, it doesn't build at all.
Anyway, I appreciate any thoughts/suggestions you have.
Mike
Tyler Nielsen wrote:
Mike,
Have you ran "libtoolize --copy --force"? Does it give an error?
As far as changing a existing plugin. You will have to edit
src/Makefile.am then run automake to change which files it
compiles. Then run autogen.sh. I 'm not much good at automake,
but I know there are other settings at the top level that you
can/should edit also. Package name for example. You also
probably want to change the .so you are making. This is also
done in src/Makefile.am.
If you copy an existing plugin, or use the gst-template, you
still have to make the same changes to the automake files.
Unless you want your plugin called libgstplugin.so.
Tyler
On Mon, Apr 21, 2008 at 11:58 PM, Mike Patton
<[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:
Hey all,
I have downloaded and successfully built the ti plugins for
the Davinci gstreamer, but I want to make a plugin of my own.
I have read the gstreamer plugin writers guide, and thought
I'd start from the gst-template.
That only comes with a autogen.sh to make everything, and it
bombs with the following error:
configure: error:
*** [Gentoo] sanity check failed! ***
*** libtool.m4 and ltmain.sh have a version mismatch! ***
*** (libtool.m4 = 1.5.26, ltmain.sh = 1.5.8) ***
Please run:
libtoolize --copy --force
I have also tried to just copy one of the ti_plugin dir, and
wanted to just replace the source files with mine, and edit
the makefile appropriately, but I failed.
I'm clearly not as well versed in this build procedure as I
thought.
Can anyone either
a) tell me how to get the gst-template to build using a cross
compile
b) give/point to a few simple steps on how to build a new
plugin, (beyond what's in the plugins' writers guide)
or
c)suggest how to copy an existing, building plugin and modify
it to just use my source files and then cross compile.
Sorry for my ignorance,
Mike
_______________________________________________
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
<mailto:Davinci-linux-open-source@linux.davincidsp.com>
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
_______________________________________________
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
