Developing Slackware installation procedure

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Developing Slackware installation procedure

catkin
Hello

I would like to develop a LibreCAD installation procedure for Slackware (Slackware64 13.1) but have encountered a qmake problem and do not know enough about qmake to debug it.

Using the Ubuntu 10.10 installation procedure as a basis, I downloaded the git, ran qmake (which generated Makefile and two directories) and ran qmake Makefile which generated the following error:

Makefile:1079: Parse Error ('first: all')

Netsearching suggested this is caused by an error in the .pro file but librecad.pro does not contain anything to generate "first: all" to my unlearned eyes.

What to do?

Incidentally the Ubuntu 10.10 installation procedure has lines run together such as "cd ~  mkdir source  cd source" and there's a typo in "Note: if you have 1t3 and qt4".  EDIT: It also has "cd LibreCAD qmake make" which should (?) be "cd LibreCAD && qmake && qmake Makefile".

Best

Charles

Reply | Threaded
Open this post in threaded view
|

Re: Developing Slackware installation procedure

R. van Twisk
Administrator

On Jun 27, 2011, at 10:13 PM, catkin [via LibreCAD] wrote:

Hello

I would like to develop a LibreCAD installation procedure for Slackware (Slackware64 13.1) but have encountered a qmake problem and do not know enough about qmake to debug it.

Using the Ubuntu 10.10 installation procedure as a basis, I downloaded the git, ran qmake (which generated Makefile and two directories) and ran qmake Makefile which generated the following error:

Makefile:1079: Parse Error ('first: all')

Netsearching suggested this is caused by an error in the .pro file but librecad.pro does not contain anything to generate "first: all" to my unlearned eyes.

What to do?

Charles,

I will take a look at the CMS and see why it appears on one line...

However, it sounds like if you are running qmake on the makefile.

The process is like this:

first execute : qmake
Wait until it finishes, then rune make

This process is also explained here:


(but instead of suing svn we now use git)

Ries



Incidentally the Ubuntu 10.10 installation procedure has lines run together such as "cd ~  mkdir source  cd source" and there's a typo in "Note: if you have 1t3 and qt4".

Best

Charles




If you reply to this email, your message will be added to the discussion below:
http://librecad.1049103.n5.nabble.com/Developing-Slackware-installation-procedure-tp4530576p4530576.html
To start a new topic under LibreCAD, email [hidden email]
To unsubscribe from LibreCAD, click here.

Reply | Threaded
Open this post in threaded view
|

Re: Developing Slackware installation procedure

maqifrnswa
In reply to this post by catkin
On Mon, Jun 27, 2011 at 11:13 PM, catkin [via LibreCAD]
<[hidden email]> wrote:
>
> Hello
>
> I would like to develop a LibreCAD installation procedure for Slackware (Slackware64 13.1) but have encountered a qmake problem and do not know enough about qmake to debug it.
>
> Using the Ubuntu 10.10 installation procedureĀ as a basis, I downloaded the git, ran qmake (which generated Makefile and two directories) and ran qmake Makefile which generated the following error:
>
> Makefile:1079: Parse Error ('first: all')

I can repeat your error if I do the following:
$ qmake
$ qmake Makefile

which is incorrect

you should be doing (as Ries pointed out above)
$ qmake
$ make


When I use "make" instead of "qmake Makefile", the program builds.

Hopefully that works for you too
Reply | Threaded
Open this post in threaded view
|

Re: Developing Slackware installation procedure

catkin
Thanks Ries and showard314

That was exactly my error.  After fixing that:
[compilation completed]
scripts/postprocess-unix.sh
Reading collection config file...
Generating help for LibreCADdoc.qhp...
Building up file structure...
Insert custom filters...
Insert help data for filter section (1 of 1)...
Insert files...
Warning: The file /home/c/d/Repository/src/git/LibreCAD/support/doc/appendix_LibreCAD1.html does not exist! Skipping it.
Insert contents...
Insert indices...
Documentation successfully generated.
Creating collection file...
Updating '/home/c/d/Repository/src/git/LibreCAD/ts/librecad_cs.qm'...
    Generated 1556 translation(s) (1448 finished and 108 unfinished)
[snip similar for other languages]
    Ignored 184 untranslated source text(s)
lrelease error: Cannot open /home/c/d/Repository/src/git/LibreCAD/ts/librecad_sv.ts: No such file or directory
After that I tested the build by running
cd unix && ./librecad
It opened LibreCAD OK; it looked fine and I drew a few lines OK.

Installing LibreCAD from source would be easier to follow if the commands which should be on separate lines were shown on separate lines or the commands were separated by appropriate shell metacharacters (and the Java syntax highlighting could be removed because it is not meaningful).  For example
cd ~  mkdir source  cd source  git clone git://github.com/LibreCAD/LibreCAD.git
would be
cd ~  && mkdir source  && cd source  && git clone git://github.com/LibreCAD/LibreCAD.git
and
cd LibreCAD qmake make
would become
cd LibreCAD && qmake && make
or, if qmake return code is not useful/reliable, simply
cd LibreCAD && qmake; make
I am willing to change the page.

Best

Charles
Reply | Threaded
Open this post in threaded view
|

Re: Developing Slackware installation procedure

R. van Twisk
Administrator
Charles,

I will take care of the breaks later today.
This seems to be a issue with the highlighter plugin we are using..

Ries
On Jun 28, 2011, at 10:45 AM, catkin [via LibreCAD] wrote:

Thanks Ries and showard314

That was exactly my error.  After fixing that:
[compilation completed]
scripts/postprocess-unix.sh
Reading collection config file...
Generating help for LibreCADdoc.qhp...
Building up file structure...
Insert custom filters...
Insert help data for filter section (1 of 1)...
Insert files...
Warning: The file /home/c/d/Repository/src/git/LibreCAD/support/doc/appendix_LibreCAD1.html does not exist! Skipping it.
Insert contents...
Insert indices...
Documentation successfully generated.
Creating collection file...
Updating '/home/c/d/Repository/src/git/LibreCAD/ts/librecad_cs.qm'...
    Generated 1556 translation(s) (1448 finished and 108 unfinished)
[snip similar for other languages]
    Ignored 184 untranslated source text(s)
lrelease error: Cannot open /home/c/d/Repository/src/git/LibreCAD/ts/librecad_sv.ts: No such file or directory
After that I tested the build by running
cd unix && ./librecad
It opened LibreCAD OK; it looked fine and I drew a few lines OK.

Installing LibreCAD from source would be easier to follow if the commands which should be on separate lines were shown on separate lines or the commands were separated by appropriate shell metacharacters (and the Java syntax highlighting could be removed because it is not meaningful).  For example
cd ~  mkdir source  cd source  git clone <a href="git://github.com/LibreCAD/LibreCAD.git">git://github.com/LibreCAD/LibreCAD.git
would be
cd ~  && mkdir source  && cd source  && git clone <a href="git://github.com/LibreCAD/LibreCAD.git">git://github.com/LibreCAD/LibreCAD.git
and
cd LibreCAD qmake make
would become
cd LibreCAD && qmake && make
or, if qmake return code is not useful/reliable, simply
cd LibreCAD && qmake; make
I am willing to change the page.

Best

Charles



If you reply to this email, your message will be added to the discussion below:
http://librecad.1049103.n5.nabble.com/Developing-Slackware-installation-procedure-tp4530576p4532256.html
To start a new topic under LibreCAD, email [hidden email]
To unsubscribe from LibreCAD, click here.

Reply | Threaded
Open this post in threaded view
|

Re: Developing Slackware installation procedure

catkin
In reply to this post by catkin
Hello

Is it OK to ignore the two messages about missing files?

LibreCAD was OK in further use except for crashing a few times when a circle radius was copy-pasted from OOo Calc.  Will keep a file to reproduce the problem when not tired and in a hurry to get a drawing done.

And so on to packaging for Slackware as a Slackbuild.  The Slackware way is to build from source and to make minimal practicable changes to upstream -- which would include MIME type and desktop integration.  The Slackbuild system requires a download link for the source.  Is it too early in LibreCAD's evolution for that?

Best

Charles