* cygport does not automatically generate dependencies
@ 2020-06-12 5:44 DRC
2020-06-12 7:03 ` ASSI
0 siblings, 1 reply; 4+ messages in thread
From: DRC @ 2020-06-12 5:44 UTC (permalink / raw)
To: cygwin-apps
I am attempting to create a new Cygwin package for my open source
software (VirtualGL) using cygport. The package is generated correctly,
but the "requires" field in the auto-generated hint is empty. The
documentation for cygport implies that it should automatically generate
package dependencies. I've spent the last two hours googling for a
solution, to no avail. What am I missing? The package builds three
executables that should depend on libGL1, libX11_6, libXext6, libXtst6,
and libturbojpeg0.
DRC
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: cygport does not automatically generate dependencies
2020-06-12 5:44 cygport does not automatically generate dependencies DRC
@ 2020-06-12 7:03 ` ASSI
2020-06-12 9:29 ` Marco Atzeri
0 siblings, 1 reply; 4+ messages in thread
From: ASSI @ 2020-06-12 7:03 UTC (permalink / raw)
To: cygwin-apps
DRC via Cygwin-apps writes:
> I am attempting to create a new Cygwin package for my open source
> software (VirtualGL) using cygport. The package is generated correctly,
> but the "requires" field in the auto-generated hint is empty. The
> documentation for cygport implies that it should automatically generate
> package dependencies.
That only works when you don't cross-compile and you didn't say whether
you are or not.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: cygport does not automatically generate dependencies
2020-06-12 7:03 ` ASSI
@ 2020-06-12 9:29 ` Marco Atzeri
2020-06-12 15:06 ` DRC
0 siblings, 1 reply; 4+ messages in thread
From: Marco Atzeri @ 2020-06-12 9:29 UTC (permalink / raw)
To: cygwin-apps
On 12.06.2020 09:03, ASSI wrote:
> DRC via Cygwin-apps writes:
>> I am attempting to create a new Cygwin package for my open source
>> software (VirtualGL) using cygport. The package is generated correctly,
>> but the "requires" field in the auto-generated hint is empty. The
>> documentation for cygport implies that it should automatically generate
>> package dependencies.
>
> That only works when you don't cross-compile and you didn't say whether
> you are or not.
and if you have installed the cygwin packages for the build
and you are not using your own hand installed one.
cygport --debug <cygport_file> deps
will be very verbose on the dependencies check
> Regards,
> Achim.
>
Regards
Marco
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: cygport does not automatically generate dependencies
2020-06-12 9:29 ` Marco Atzeri
@ 2020-06-12 15:06 ` DRC
0 siblings, 0 replies; 4+ messages in thread
From: DRC @ 2020-06-12 15:06 UTC (permalink / raw)
To: cygwin-apps
On 6/12/20 4:29 AM, Marco Atzeri via Cygwin-apps wrote:
>> That only works when you don't cross-compile and you didn't say whether
>> you are or not.
>
> and if you have installed the cygwin packages for the build
> and you are not using your own hand installed one.
>
> cygport --debug <cygport_file> deps
>
> will be very verbose on the dependencies check
I figured it out. Apparently the cygport script requires .exe files to
have execute permissions in order to check dependencies on them, and for
whatever reason, when running my build on a shared network drive, those
files weren't created with the correct permissions. I ran the build on
a local drive, and it works properly now.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2020-06-12 15:06 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-06-12 5:44 cygport does not automatically generate dependencies DRC
2020-06-12 7:03 ` ASSI
2020-06-12 9:29 ` Marco Atzeri
2020-06-12 15:06 ` DRC
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).