* Re: [RFC] cygport: arch-specific workdir
2014-03-27 18:50 ` [RFC] cygport: arch-specific workdir (was: cygport cross compilation) Yaakov (Cygwin/X)
@ 2014-03-27 20:01 ` Achim Gratz
2014-03-27 21:02 ` Ken Brown
2014-03-27 23:47 ` David Stacey
` (2 subsequent siblings)
3 siblings, 1 reply; 12+ messages in thread
From: Achim Gratz @ 2014-03-27 20:01 UTC (permalink / raw)
To: cygwin-apps
Yaakov (Cygwin/X) writes:
>> Actually, that is experimental code (based on a request from another
>> cygport user) that was accidentally shipped when I had to reroll the
>> source tarball for compatibility with F20/UnversionedDocDirs. Would
>> people like to see this done always, never, or only when cross-building?
>
> There hasn't been much comment on this. Since it would be a visible
> change for package maintainers, I would appreciate more of a
> consensus. Are there any objections to making the workdir always
> arch-specific (IOW name-ver-rel.arch)?
I would rather have {build,inst,dist}/<arch> directories inside the
workdir so the same package could build for both x86 and x86_64 in one
workdir.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [RFC] cygport: arch-specific workdir
2014-03-27 20:01 ` [RFC] cygport: arch-specific workdir Achim Gratz
@ 2014-03-27 21:02 ` Ken Brown
0 siblings, 0 replies; 12+ messages in thread
From: Ken Brown @ 2014-03-27 21:02 UTC (permalink / raw)
To: cygwin-apps
On 3/27/2014 4:01 PM, Achim Gratz wrote:
> Yaakov (Cygwin/X) writes:
>>> Actually, that is experimental code (based on a request from another
>>> cygport user) that was accidentally shipped when I had to reroll the
>>> source tarball for compatibility with F20/UnversionedDocDirs. Would
>>> people like to see this done always, never, or only when cross-building?
>>
>> There hasn't been much comment on this. Since it would be a visible
>> change for package maintainers, I would appreciate more of a
>> consensus. Are there any objections to making the workdir always
>> arch-specific (IOW name-ver-rel.arch)?
>
> I would rather have {build,inst,dist}/<arch> directories inside the
> workdir so the same package could build for both x86 and x86_64 in one
> workdir.
That would be inconvenient for the situation where you have to do a new
build (and bump the release number) for only one arch. Also, there
might be arch-specific patches, requiring arch-specific src and origsrc
directories, so you don't really save any disk space by having a common
workdir.
Ken
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [RFC] cygport: arch-specific workdir
2014-03-27 18:50 ` [RFC] cygport: arch-specific workdir (was: cygport cross compilation) Yaakov (Cygwin/X)
2014-03-27 20:01 ` [RFC] cygport: arch-specific workdir Achim Gratz
@ 2014-03-27 23:47 ` David Stacey
2014-03-28 17:20 ` David Rothenberger
2014-04-27 20:22 ` Yaakov (Cygwin/X)
3 siblings, 0 replies; 12+ messages in thread
From: David Stacey @ 2014-03-27 23:47 UTC (permalink / raw)
To: cygwin-apps
On 27/03/14 18:50, Yaakov (Cygwin/X) wrote:
>> Actually, that is experimental code (based on a request from another
>> cygport user) that was accidentally shipped when I had to reroll the
>> source tarball for compatibility with F20/UnversionedDocDirs. Would
>> people like to see this done always, never, or only when cross-building?
>
> There hasn't been much comment on this. Since it would be a visible
> change for package maintainers, I would appreciate more of a
> consensus. Are there any objections to making the workdir always
> arch-specific (IOW name-ver-rel.arch)?
I wrapped Cygport some time ago to give me a little extra functionality
- for instance, for each package I maintain, it polls the project web
page daily and does some regexp to see if a new version of the package
had been released. If so, a new .cygport file is made and Cygport
invoked to build, test and package the application.
So any change to Cygport would give me a little maintenance, but I could
probably cope with a directory rename! Besides, some maintenance on my
builder is a bit overdue: the tool is still uploading binaries to my
Dropbox account and preparing [RFU] e-mails :-)
Dave.
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [RFC] cygport: arch-specific workdir
2014-03-27 18:50 ` [RFC] cygport: arch-specific workdir (was: cygport cross compilation) Yaakov (Cygwin/X)
2014-03-27 20:01 ` [RFC] cygport: arch-specific workdir Achim Gratz
2014-03-27 23:47 ` David Stacey
@ 2014-03-28 17:20 ` David Rothenberger
2014-04-27 20:22 ` Yaakov (Cygwin/X)
3 siblings, 0 replies; 12+ messages in thread
From: David Rothenberger @ 2014-03-28 17:20 UTC (permalink / raw)
To: cygwin-apps
Yaakov (Cygwin/X) wrote:
> On 2014-03-19 13:04, Yaakov (Cygwin/X) wrote:
>> On 2014-03-19 11:32, Ken Brown wrote:
>>> I've just started experimenting with using cygport for cross compiling,
>>> and I've come across two issues:
>>>
>>> 1. This is just a request: The latest cygport for Fedora appends i686 or
>>> x86_64 to the name of the working directory. I would find it convenient
>>> if cygport did the same thing on Cygwin, at least if the --32 or --64
>>> option is specified.
>>
>> Actually, that is experimental code (based on a request from another
>> cygport user) that was accidentally shipped when I had to reroll the
>> source tarball for compatibility with F20/UnversionedDocDirs. Would
>> people like to see this done always, never, or only when cross-building?
>
> There hasn't been much comment on this. Since it would be a visible
> change for package maintainers, I would appreciate more of a consensus.
> Are there any objections to making the workdir always arch-specific
> (IOW name-ver-rel.arch)?
I would favor making the workdir always arch-specific. It would allow me
to build my package for both archs at the same time. Currently, I have
to build for one, move the created packages, then rebuild for the other
arch.
--
David Rothenberger ---- daveroth@acm.org
"Indecision is the basis of flexibility"
-- button at a Science Fiction convention.
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [RFC] cygport: arch-specific workdir
2014-03-27 18:50 ` [RFC] cygport: arch-specific workdir (was: cygport cross compilation) Yaakov (Cygwin/X)
` (2 preceding siblings ...)
2014-03-28 17:20 ` David Rothenberger
@ 2014-04-27 20:22 ` Yaakov (Cygwin/X)
2014-05-04 16:41 ` Achim Gratz
3 siblings, 1 reply; 12+ messages in thread
From: Yaakov (Cygwin/X) @ 2014-04-27 20:22 UTC (permalink / raw)
To: cygwin-apps
On 2014-03-27 13:50, Yaakov (Cygwin/X) wrote:
> On 2014-03-19 13:04, Yaakov (Cygwin/X) wrote:
>> On 2014-03-19 11:32, Ken Brown wrote:
>>> I've just started experimenting with using cygport for cross compiling,
>>> and I've come across two issues:
>>>
>>> 1. This is just a request: The latest cygport for Fedora appends i686 or
>>> x86_64 to the name of the working directory. I would find it convenient
>>> if cygport did the same thing on Cygwin, at least if the --32 or --64
>>> option is specified.
>>
>> Actually, that is experimental code (based on a request from another
>> cygport user) that was accidentally shipped when I had to reroll the
>> source tarball for compatibility with F20/UnversionedDocDirs. Would
>> people like to see this done always, never, or only when cross-building?
This is now in git master.
Yaakov
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [RFC] cygport: arch-specific workdir
2014-04-27 20:22 ` Yaakov (Cygwin/X)
@ 2014-05-04 16:41 ` Achim Gratz
0 siblings, 0 replies; 12+ messages in thread
From: Achim Gratz @ 2014-05-04 16:41 UTC (permalink / raw)
To: cygwin-apps
Yaakov (Cygwin/X) writes:
> This is now in git master.
How about this change? I'm usually having $arch set in my shell to
divert the build results to the proper release directories, and having
yet another naming convention doesn't really help with that.
bin/cygport.in: follow Cygwin convention for directory naming (x86 instead of i686)
diff --git a/bin/cygport.in b/bin/cygport.in
index 943d391..2ecfc25 100755
--- a/bin/cygport.in
+++ b/bin/cygport.in
@@ -672,7 +672,7 @@ unset restrict
#
################################################################################
-declare -r workdir="${top}/${$PF}.${ARCH}";
+declare -r workdir="${top}/${$PF}.${ARCH/i686/x86}";
declare -r srcdir="${workdir}/src";
declare -r origsrcdir="${workdir}/origsrc";
declare -r configdir="${workdir}/config";
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
^ permalink raw reply [flat|nested] 12+ messages in thread