GNOME.org
 

Re: [Vala] Launched version 1.14 of Autovala

I just tried autovala(Ubuntu 18.04), but getting an error. Witch packet is missing? 

The Meson build system
Version: 0.45.1
Source dir: /home/wolfgang/autovala
Build dir: /home/wolfgang/autovala/meson
Build type: native build
Project name: autovala
Native C compiler: cc (gcc 7.3.0 "cc (Ubuntu 7.3.0-27ubuntu1~18.04) 7.3.0")
Native Vala compiler: valac (valac unknown version)
Build machine cpu family: x86_64
Build machine cpu: x86_64
Program pandoc found: YES (/usr/bin/pandoc)
Program curl found: YES (/usr/bin/curl)
Program g-ir-scanner found: YES (/usr/bin/g-ir-scanner)
Program glib-compile-resources found: YES (/usr/bin/glib-compile-resources)
Program g-ir-compiler found: YES (/usr/bin/g-ir-compiler)
Found pkg-config: /usr/bin/pkg-config (0.29.1)
Native dependency atk found: YES 2.28.1
Native dependency gio-2.0 found: YES 2.56.3
Native dependency gtk+-3.0 found: YES 3.22.30
Native dependency x11 found: YES 1.6.4
Native dependency cairo found: YES 1.15.10
Native dependency gdk-3.0 found: YES 3.22.30
Native dependency gdk-pixbuf-2.0 found: YES 2.36.11
Native dependency gee-0.8 found: YES 0.20.1
Native dependency glib-2.0 found: YES 2.56.3
Native dependency gobject-2.0 found: YES 2.56.3
Native dependency libxml-2.0 found: YES 2.9.4
Native dependency pango found: YES 1.40.14
Native dependency pangocairo found: YES 1.40.14
Native dependency vte-2.91 found: YES 0.52.2
Program /home/wolfgang/autovala/meson_scripts/install_data.sh found: YES (/home/wolfgang/autovala/meson_scripts/install_data.sh) 
Program glib-compile-resources found: YES (/usr/bin/glib-compile-resources)
Program /home/wolfgang/autovala/meson_scripts/install_manpage.sh found: YES (/home/wolfgang/autovala/meson_scripts/install_manpage.sh)
meson.build:80:1: ERROR: Problem encountered: The file /usr/include/readline/readline.h must exist to compile this project. 


Am 07.04.19 um 20:30 schrieb rastersoft:
In autovala, the .avprj file contains a description of the whole project, including not only the binaries, but also icons, glade files, documentation... The file, by default, is generated automagically by autovala, but the programmer can tweak it to adapt it to its project.
So maybe the best solution is to do an "autovala translator" that takes your files and creates a basic autovala project file with only the parts known by it, and then run autovala to complete it with all the parts not known by valadevelop, like manpages... 

El 7/4/19 a las 19:45, Wolfgang Mauer escribió:

I have just read the "3 Steps"....
Hmmm, in valaDevelop the "master" is a solution file witch can contain 1 or more project files, not the content of folders and files 

A project file contains resources, packages and sourcefiles...

VS.vsln:
<?xml version="1.0" encoding="utf-8"?>
<!--generated by valaDevelop-->
<Item Type="1" Name="VS">
    <Item Type="34" Name="VP" Path="./VP"/>
    <Item Type="34" Name="sharedProject" Path="./sharedProject"/>
    <Breakpoints>
        <Breakpoint Filename="/home/wolfgang/Projekte/VS/VP/main.vala" Line="24"/>         <Breakpoint Filename="/home/wolfgang/Projekte/VS/VP/main.vala" Line="12"/> 
    </Breakpoints>
    <Bookmarks/>
</Item>

VP.vprj:
<?xml version="1.0"?>
<!--generated by valaDevelop-->
<Item Type="34" Name="VP" Namespace="VP" BuildType="4" WithVapi="false" Path="./VP" BuildCommand="" CompilerOptions="" DebugBreakCriticals="true" DebugBreakWarnings="false"> 
    <Comment></Comment>
    <Item Type="48" Name="References">
        <Item Type="80" Name="sharedProject"/>
        <Item Type="16" Name="gtk+-3..0"/>
    </Item>
    <Item Type="36" Name="Resources" Path="./VP/resources">
        <Item Type="4" Name="GladeDialog.glade" BuildType="2" ResourceId="/VP/GladeDialog.glade" ResourceCompress="true" ResourceStripBlanks="true" ResourceAlias=""/>         <Item Type="4" Name="window.glade" BuildType="2" ResourceId="/VP/window.glade" ResourceCompress="false" ResourceStripBlanks="false" ResourceAlias=""/> 
    </Item>
    <Item Type="8" Name="main.vala" BuildType="1"/>
    <Item Type="8" Name="myNewDialog.vala" BuildType="1"/>
</Item>

sharedProject.vprj:
<?xml version="1.0"?>
<!--generated by valaDevelop-->
<Item Type="34" Name="sharedProject" Namespace="sharedProject" BuildType="5" WithVapi="true" Path="./sharedProject" BuildCommand="" CompilerOptions="" DebugBreakCriticals="false" DebugBreakWarnings="false"> 
    <Comment></Comment>
    <Item Type="48" Name="References">
        <Item Type="16" Name="gtk+-3..0"/>
    </Item>
    <Item Type="36" Name="Resources" Path="./sharedProject/resources"/>
    <Item Type="32" Name="ABC" Path="./sharedProject/ABC">
        <Item Type="8" Name="EmptyClass.vala" BuildType="1"/>
    </Item>
    <Item Type="8" Name="main.vala" BuildType="1"/>
</Item>



Am 07.04.19 um 19:27 schrieb rastersoft:


Mmmm... yes, in theory it could be used, yes.

El 7/4/19 a las 19:20, Wolfgang Mauer escribió:
So Autovala could be used by valaDevelop to create all necessary files for an "external build" 
?
Am 07.04.19 um 18:14 schrieb rastersoft:

Hi all:
I just launched version 1.14.0 of Autovala, the project manager for Vala that simplifies and automates the creation of the CMake and Meson files for a Vala (and/or C) project. This version fixes several bugs with Meson when the installation path is not the standard one, and also finally doesn't install the CMakeList.txt files when using Ninja.
As usual, you can download it from my homepage: https://www.rastersoft.com/programas/autovala..html 


--
Nos leemos
                         RASTER    (Linux user #228804)
raster rastersoft com               http://www.rastersoft.com


--
Nos leemos
                         RASTER    (Linux user #228804)
raster rastersoft com               http://www.rastersoft.com
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]