Progress with auto*

H

Thread Starter

hopfgartner

Dear lovers of free PLCs,

I've worked again a bit on auto* support in linuxplc. Those curious about this topic can mail me for a copy of the files.

Anyway, I have some issues:

1) in logic/iec compilation (original build setup) stops with the error message in the attachment.

2) Should the files in drivers be build as libraries?

Thank you for your kind attention.

As always yours,

Peter

_______________________________________________
LinuxPLC mailing list
[email protected]
http://linuxplc.org/mailman/listinfo/linuxplc
 
M

Mario de Sousa

Peter,

The code under

/logic/iec
/logic/plc5

is incomplete, and does not compile correctly. Do not bother with these directories for the moment.

The code in the drivers directory should build linux device drivers, i.e. they should generate object (*.o) files. Note that the
/drivers/cif
directory comes only with two *.tgz files, obtained from www.hilscher.com. These files need merely to be unziped. The compiled version of the driver is already included, although it might not be a bad idea to recompile for the user's kernel verion. Use the file cifv1003.tgz for kernels 2.2.*, and cifv2000.tgz for kernels 2.4.* I have created a small shell script in this directory that figures out which kernel the user is using, and will unzip the correct file. Note that each of these zipped files will generate a slightly different directory structure, which is not good because the cif module (/io/cif) needs to know where to find the relevant files. That is why that same script also creates some symbolic links, so that the cif module can find the files in the same directory, no matter which version is being used.

The driver under /drivers/8255 also needs to be updated (I haven't got round to it yet). At the moment it will only compile under 2.2.* kernels. I believe Curt has obtained updated drivers, but they haven't been commited to the cvs yet.

Cheers,

Mario.

----------------------------------------------------------------------------
Mario J. R. de Sousa
[email protected]
----------------------------------------------------------------------------

The box said it requires Windows 95 or better, so I installed Linux

_______________________________________________
LinuxPLC mailing list
[email protected]
http://linuxplc.org/mailman/listinfo/linuxplc
 
H
On Tue, 23 Oct 2001 13:09:18 +0100
Mario de Sousa <[email protected]> wrote:
> hopfgartner wrote:
> >
> > I've worked again a bit on auto* support in linuxplc.
> Those
> > curious about this topic can mail me for a copy of the
> > files.
> >
> > Anyway, I have some issues:
> >
> > 1) in logic/iec compilation (original build setup)
> stops
> > with the error message in the attachment.
> >
> > 2) Should the files in drivers be build as libraries?
>
> Peter,
>
> The code under
>
> /logic/iec
> /logic/plc5
>
> is incomplete, and does not compile correctly. Do not
> bother with these
> directories for the moment.

Good, less work for the moment!

> The code in the drivers directory should build linux
> device drivers,

Uuuuh, I have not yet seen Linux kernel modules that have been build with auto*. This will bring my lonely neuron to fusion. I will try to find out how something like that can be done. Certainly, this would ease the installation of
kernel modules a lot.

I could try to do something like the following:

1) try to find out where the kernel headers are (I think that this can be hard, since it seems to depend on the distribution).

2) compile the modules

3) install them in the appropriate places /lib/whatever, when 'make install' is invoked.

Anyway, I will try to do everything else first.

Should we arrive to a point where distribution packages are released (.deb, .rpm or whatever), then we should separate the drivers from the rest and build distinct packages.

Ok,

I will inform you on the proceedings. In the mean time, have
fun,

Peter
_______________________________________________
LinuxPLC mailing list
[email protected]
http://linuxplc.org/mailman/listinfo/linuxplc

 
M

Mario de Sousa

hopfgartner wrote:

> > The code in the drivers directory should build linux
> > device drivers,
>
> Uuuuh, I have not yet seen Linux kernel modules that have
> been build with auto*. This will bring my lonely neuron to
> fusion. I will try to find out how something like that can
> be done. Certainly, this would ease the installation of
> kernel modules a lot.
>
> I could try to do something like the following:
>
> 1) try to find out where the kernel headers are (I think
> that this can be hard, since it seems to depend on the
> distribution).
>

And not only that, some people ;-) may have more than one version of the kernel source installed simultaneously...

I don't have much experience with many distributions, but I believe that the headers are usually under /usr/include/linux. You can get the
version from /usr/include/linux/version.h.

You can get the version of the currently executing kernel from
/proc/version

The script under /drivers/cif uses /proc/version to figure out which version to unzip, while the makefile under /drivers/8255 uses the
/usr/include/linux/version.h file.

I don't know whether the auto* tools will be much use here. Maybe just have the top level install call the install scripts in each of the
drivers? But then again, I have been wrong before...

BTW, don't worry too much with the /io/modbus directory. I am working on that code right now, and will most probably change the file structure. I have not committed my current version yet mostly because I am not yet sure how the final file structure will look like, and cvs is kind of a bother to make these kinds of changes. I'll commit what I have as soon as I make a final decision on the new file structure.

Cheers,

Mario.

----------------------------------------------------------------------------
Mario J. R. de Sousa
[email protected]
----------------------------------------------------------------------------

The box said it requires Windows 95 or better, so I installed Linux

_______________________________________________
LinuxPLC mailing list
[email protected]
http://linuxplc.org/mailman/listinfo/linuxplc
 
Top