[Elphel-support] Compiling bug fix for VLC streaming

[Andrey Filippov]

Eric, ETRAX is little-endian.

Are you trying just to try the driver in the camera or prepare it to
be included in the camera software for others?
In any case, to make the software built it has either be included in
http://elphel.cvs.sourceforge.net/viewvc/elphel/elphel353-8.0/subdirs.list?view=markup
or one of the higher level Makefile should invoke it - directly or
indirectly

The second requires more steps (and independent testing that it does
not break things for others before being included) and we'll
definitely try to help. If the driver is small and contains few files
it can be just copied to the source tree. If it is a port of a large
package, it should be installed/patched from the original location. In
that case:
1- it should be referenced in
http://elphel.cvs.sourceforge.net/viewvc/elphel/elphel353-8.0/configure-files/post?view=markup
, the copy should be uploaded to our mirror so installation will not
fail if one of the other sites is down (or changed/removed the needed
file/version)
2 - it should have configure_elphel (like here:
http://elphel.cvs.sourceforge.net/viewvc/elphel/elphel353-8.0/apps/php-5.2.9/)
- that file is responsible for patching the source to port it to the
camera
3 - src.list should include all new files and synchronized with the
CVS. src list is used to create the modified distribution
4 - target.list - I already explained earlier is needed to verify that
all files installed (different packages install differently and do not
have a single way to verify installation)

The first step to verify the new modified distribution (that you can
make yourself, before committing to the CVS) - download the newly
generated tar.gz file and build it on the other computer (or at least
in the directory, that does not see "distfiles" - cache of the
downloaded  archives), so the build script will have to download
everything from the Internet.

Andrey

On Fri, Feb 24, 2012 at 3:30 PM, Eric Boudrand <dev at boudrand.net> wrote:
> Andrey,
>
> Thanks for the explanation.
>
> I am reading AXIS SDK documentation in configure-file/source. Is there
> an example how to create and add a package in the image ?
>
> I could compile driver rtl8712u with cris compiler. But, is ETRAX FS
> processor little endian or big endian ?
>
> Thanks.
>
> Éric
>
>
> Le vendredi 24 février 2012 à 11:13 -0700, Andrey Filippov a écrit :
>> Eric,
>>
>> target.list is used only for the verification, it does not replace
>> functionality of the of "configure" or "Makefile". When everything is
>> "installed" (on the host computer), the build script make a list of
>> the installed files and directories, creates target.list.new and
>> diff-s it with the saved target.list reporting any differences. The
>> new built image includes archived source tree (as in /* source is
>> inside */), and that archive has the target.list matching the archived
>> source, so if you build from that archive - target.list should match.
>>
>> We did have problems when some files were missing on the host
>> computer, and ion the result the built system mas missing some needed
>> files. Of course, the problems were reported in some long build.log
>> files, but it was difficult to notice them. That was why we
>> implemented the target.list - just to make sure all the files that
>> were supposed to be installed are actually installed.
>>
>> Andrey
>>
>
>
>
> _______________________________________________
> Support-list mailing list
> Support-list at support.elphel.com
> http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com