mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] PTXdist: New cmake package (webtoolkit wt)
Date: Sat, 04 May 2013 12:05:52 +0200	[thread overview]
Message-ID: <d0d6d566ef0d4b310d2a65f90297a2e4@idefix.lespocky.dyndns.org> (raw)
In-Reply-To: <9E0B7EF1EDF3FF49A8B173782CCEC62D04C5AA8D@gea-exchange-02.net.gantner.com>

Hei hei, 
Am 2013-04-22 16:33, schrieb Stranz Jan-Marc:
> I created new rules for that package with 
> ptxdist newpackage target
> But these rules a based on "autotools" rather than on "cmake".

Go like this but just change the stuff in the .in and .make rule.

> What should I do?
> Is there an application note for a packages based on "cmake"?

Not to my knowledge, but we use cmake for all our packages. I can give
you some hints.

First: include a line 

  select HOST_CMAKE

in your rules/foo.in so you are sure you can use cmake for build.

In your make file you can go with the default stages, but you have to
adapt the prepare stage. Just set

  FOO_CONF_TOOL := cmake

and give it a try. You can pass additional options for example with

  FOO_CONF_OPT += -DSOME_OPTION_IN_YOUR_CMAKE_LIST_FILE:STING="foobar"

That's all, basically, if your CMake based project does not do any
weird things.

HTH & Greets
Alex

-- 
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601  D1D5 8FBA 7744 CC87 10D0 ***

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  parent reply	other threads:[~2013-05-04 10:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-22 14:33 Stranz Jan-Marc
2013-04-22 15:07 ` Josef Holzmayr
2013-05-04 10:05 ` Alexander Dahl [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-04-22 14:05 Stranz Jan-Marc

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d0d6d566ef0d4b310d2a65f90297a2e4@idefix.lespocky.dyndns.org \
    --to=post@lespocky.de \
    --cc=ptxdist@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox