public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: matthias@koefferlein.de
To: cygwin@cygwin.com
Subject: qmake-qt5 does not support QMAKE_POST_LINK on shared object targets
Date: Tue, 25 Feb 2020 14:40:00 -0000	[thread overview]
Message-ID: <20200225153950.Horde.z195jFsJbgwsyFSP_AqtyQ3@webmail.df.eu> (raw)

Dear qt5-base maintainers,

I noticed that QMAKE_POST_LINK is not applied to shared object targets  
in qmake (version 3.1 from Qt 5.9.4). The purpose of QMAKE_POST_LINK  
is to add custom script statements after the link step in  
qmake-generated Makefiles.

I checked cygwin's package files for qt5-base and found this patch  
which IMHO is lacking QMAKE_POST_LINK support.

The qmake.patch is taken from here:

https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/qt5-base.git;a=blob;f=5.9-cygwin-qmake.patch;h=e6feef3d3a19e5e412adf6e4f2b9ac512553cdc1;hb=HEAD

I am referring to this part of the qmake.patch file:

   72              if (!isystem.isEmpty() && isSystemInclude(inc.toQString()))
   73 @@ -603,6 +603,14 @@ UnixMakefileGenerator::writeMakeParts(QT
   74              if(!project->isEmpty("QMAKE_POST_LINK"))
   75                  t << "\n\t" << var("QMAKE_POST_LINK");
   76              t << endl << endl;
   77 +        } else if(!project->isEmpty("QMAKE_CYGWIN_SHLIB")) {
   78 +            t << "\n\t"
   79 +              << "-$(DEL_FILE) $(TARGET) $(TARGET0)" << "\n\t"
   80 +              << var("QMAKE_LINK_SHLIB_CMD") << "\n\t";
   81 +            if(!destdir.isEmpty())
   82 +              t  << "-$(DEL_FILE) " << destdir << "$(TARGET)\n\t"
   83 +                 << "-$(DEL_FILE) " << destdir << "$(TARGET0)\n\t"
   84 +                 << "-$(MOVE) $(TARGET) $(TARGET0) " << destdir;
----
# IMHO this part of the patch is missing to enable QMAKE_POST_LINK:
                   if(!project->isEmpty("QMAKE_POST_LINK"))
                       t << "\n\t" << var("QMAKE_POST_LINK");
                   t << endl << endl;
----
   85          } else if(project->isEmpty("QMAKE_HPUX_SHLIB")) {
   86              t << "\n\t";
   87


Thanks for considering this bug report.

Best regards,

Matthias

-----Original Message-----
From: Gratz Achim (IFD PMM TI ICTD) <Achim.Gratz@infineon.com>
Sent: Dienstag, 25. Februar 2020 09:26
To: Koefferlein Matthias (IFAG DES TCP FLP)  
<Matthias.Koefferlein@infineon.com>
Subject: RE: KLayout cygwin build

Hallo Matthias,

> Ok, verstehe. Dann ist der execinfo-Patch auch eine Lösung - es geht
> ja nur um den crash handler.

Genauer um den Stacktrace.

> Das build-Skript macht eigentlich ja nicht viel. Wenn Du die Variablen
> selber definierst, kannst Du den qmake auch direkt aufrufen. Sind aber
> halt eine Menge Variablen.

Ich krieg' das schon hin, ich muß es ja normalerweise nur einmal durchturnen.

> Ich bekomme übrigens ein:
>
> fatal: repository
> 'https://cygwin.com/git-cygwin-packages/?p=git/cygwin-
> packages/qt5-base.git/' not found
>
> :(

Probier's nochmal, irgendjemand scheint gerade den Sourceware-Server zu DOSen.


Mit freundlichen Grüßen.
--
mailto:Achim.Gratz@Infineon.com
HV-CMOS Technology Development and Process Integration
Office: +49 351 886 17 84    Fax: +49 351 886 84 17 84

Infineon Technologies Dresden GmbH & Co. KG Sitz der Gesellschaft: Dresden
Registergericht: Dresden HRA 10404

Persönlich haftende Gesellschafterin: Infineon Technologies Dresden  
Verwaltungs GmbH Vorsitzender des Aufsichtsrats: Pantelis Haidas
Geschäftsführer: Dr. Rutger Wijburg, Raik Brettschneider Sitz der  
Gesellschaft: Neubiberg
Registergericht: München HRB 229585

----- Ende der weitergeleiteten Nachricht -----



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

                 reply	other threads:[~2020-02-25 14:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200225153950.Horde.z195jFsJbgwsyFSP_AqtyQ3@webmail.df.eu \
    --to=matthias@koefferlein.de \
    --cc=cygwin@cygwin.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).