Full Description of the compilation of Scilab

Scilab 5 的编译过程全面转向 Autotools,这是一组简化跨平台项目概念、维护和移植性的工具。文章详细介绍了 autoconf、automake 和 libtool 的作用,以及如何使用它们来添加新的源文件或模块。

  • Immutable Page
  • Comments
  • Info
  • Attachments

Full Description of the compilation of Scilab

Description

Scilab 4 and previous versions compilation process were using an outdated compilation method based on the include of series of Makefiles, I was hard and painful to maintain but also to port the Scilab build process on new platform. Scilab 5 is fully based on the autotools. There are programs which greatly simplify the conception, maintenance and portability of a multi-platform project.

Autotools are composed by a few programs :

  • autoconf (at least version 2.61)

  • automake (at least version 1.10)

  • libtool

Each one is designed for a specific task.

autoconf

From configure.ac (formely configure.in), autoconf creates the configure script which will check if libraries are available on the computer (or not), set a few flags for the compiler... In theory, if the configure is successful, that ensure that all the mandatory dependencies of Scilab 5 are available on the operating system.

automake

From Makefile.am and indirectly from configure.ac, for each Makefile.am declared in the configure.ac (see the macro AC_CONFIG_FILES) , automake will create the file Makefile.in. It specifies which file must be compiled, with which libs... The autogenerated makefiles contain the directive for the compilation for many compilers, operating systems & archs.

libtool

libtool, as its name says, is the tool used to create libraries (static and dynamic) managing the inherent constraints.

Advantages

There are many advantages to this migration:

  • LSB & FHS compatibly works are greatly simplified

  • Simplify the portage to new architectures and compilers
  • Facilitate the work of distribution packagers

Technical description

Important files

File

Description

configure.ac

Transformed by autoconf to create the famous ./configure, this program handles:
* all the --with-xxx & --without-xxx options
* check if headers are available and usable
* check the versions
* Manages compilation flags
* ...

m4/*

Contains all the various macros used to perform dedicated checks

Makefile.am

Defines a few important operations:
* Create the actual Scilab binary
* Build all Scilab macros
* Build the Scilab documentation
* Build the localization
* Launch all the tests

Makefile.incl.am

This file is included in each Makefile.am of a Scilab module.
It contains target for:
* Scilab macros build
* java build
* swig/giws generation
* installation of data files
* Launch tests of a specific module

modules/Makefile.am

This file contains the list of the module to build, the creation of the libscilab library

How to regenerate all the files

The best way is to call autoreconf, this command will call all the other commands (aclocal, autoconf, automake...). Otherwise, when working on the source tree, adding the option --enable-maintainer-mode to the ./configure will automatically rebuild Makefile & configure when any changes occurs

Howto

Add a new source file for compilation

  • Go into the module you want to edit
  • Edit Makefile.am and add the file where it belongs (*_C_SOURCES, *_FORTRAN_SOURCES, GATEWAY_C_SOURCES, GATEWAY_FORTRAN_SOURCES...)

  • Go into the root of the scilab source tree (cd \$SCI)

  • Type automake

This command should rebuild Makefile.in from Makefile.am

Add a new module to Scilab

  • Create your tree in \$SCI/modules/

  • Copy an already existing Makefile.am from an other module

  • Modify it in order to match your changes (sources, libraries dependencies...)
  • Edit \$SCI/modules/Makefile.am

  • Add in the variable SUBDIRS the name of your directory you just created & and add the library to the variable ALL_LIBS

  • In configure.ac, look for AC_CONFIG_FILES and add your future Makefile

  • Go into the root of the Scilab source tree (cd \$SCI)

  • Type autoreconf (make sure that you have the right versions of the autotools).

  • Relaunch the ./configure file in order to create your Makefile from your brand new Makefile.in

public: Full Description of the compilation of Scilab (last edited 2011-03-30 16:18:07 by localhost)

智能交通灯设计是现代城市交通管理中的重要环节,利用STM32单片机进行智能交通灯控制能够提高交通效率,减少交通事故。STM32是一款基于ARM Cortex-M内核的微控制器,具有高性能、低功耗的特点,广泛应用于各种嵌入式系统设计。本项目将介绍如何使用STM32单片机配合Proteus仿真软件来实现智能交通灯系统的设计。 我们需要了解STM32的基本结构和工作原理。STM32家族包含了多种型号,它们拥有不同的内存大小、外设接口和性能等级。在这个项目中,我们可能使用的是STM32F10x系列,它具备GPIO、定时器、串行通信接口等丰富的外设资源,适合交通灯控制的需求。 智能交通灯系统通常由红绿黄三色灯组成,通过特定的时序来控制各个方向的车辆和行人通行。在设计时,我们需要考虑以下几个关键知识点: 1. **硬件接口设计**:STM32通过GPIO口连接到交通灯的LED驱动电路,设置GPIO的工作模式(如推挽输出或开漏输出),并根据交通规则控制LED灯的亮灭。 2. **定时器配置**:利用STM32的定时器功能设定交通灯各阶段的持续时间。可以使用定时器的中断功能,在特定时间点切换交通灯状态。 3. **程序逻辑**:编写C语言程序实现交通灯的逻辑控制。这包括初始化GPIO和定时器,设置交通灯状态的切换逻辑,并处理中断服务函数。 4. **Proteus仿真**:Proteus是一款强大的电子电路仿真软件,可以模拟硬件电路运行和程序执行。在这里,我们将STM32单片机模型和交通灯模型添加到仿真环境中,运行程序并观察交通灯的正确运行。 5. **调试与优化**:在Proteus中,可以通过查看虚拟示波器或逻辑分析仪来检查信号波形,帮助定位程序中的错误。通过反复调试,优化交通灯的控制算法,确保其符合实际交通需求。 6. **全套资料**:压缩包内的资料可能包括源代码
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值