unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: Reza Housseini <reza.housseini@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Need help packaging IUP (part 1: IM)
Date: Tue, 21 Mar 2023 12:45:17 +0000	[thread overview]
Message-ID: <A04owpyDkqwQBJ5odJ5Efyou2Y_DBNceAJIwyI2CPMktMkudGly2-Xr2MPrqZNgIt2nTkKjPWTCZkZn0nZXQdXofm8T8Hb-UQSZKoDppSaE=@elenq.tech> (raw)
In-Reply-To: <e1aa4a56-86b5-f1d3-65bb-abaf14537ce5@gmail.com>

Hi Reza,
Thanks for the help!
I'll answer inline:
------- Original Message -------
On Tuesday, March 21st, 2023 at 13:25, Reza Housseini <reza.housseini@gmail.com> wrote:


> Have you tried something like
> 
> (add-before 'configure 'set-ldflags
> (lambda _
> (substitute* "tecmake.mak"
> (("STDLDFLAGS := -shared" all) (string-append all "
> -Wl,-rpath="#$output "/lib")))))
> 
> not tested though.

I'll give a try to this. I didn't try it!
Thanks!

> 
> Also it looks like a cmake project, why are you not using the
> cmake-build-system?

The CMake they use gives syntax errors and the official docs describe to use the Makefile and they don't mention the CMake.
It's probably poorly maintained.

Thanks for the help! I'll answer back when I try the STDLDFLAGS!


  reply	other threads:[~2023-03-21 12:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-20 22:44 Need help packaging IUP (part 1: IM) Ekaitz Zarraga
2023-03-20 22:59 ` Felix Lechner via
2023-03-21 12:25 ` Reza Housseini
2023-03-21 12:45   ` Ekaitz Zarraga [this message]
2023-03-21 15:43     ` Ekaitz Zarraga
2023-03-21 16:01       ` Reza Housseini

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to='A04owpyDkqwQBJ5odJ5Efyou2Y_DBNceAJIwyI2CPMktMkudGly2-Xr2MPrqZNgIt2nTkKjPWTCZkZn0nZXQdXofm8T8Hb-UQSZKoDppSaE=@elenq.tech' \
    --to=ekaitz@elenq.tech \
    --cc=help-guix@gnu.org \
    --cc=reza.housseini@gmail.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).