On 7/23/2012 9:44 PM, Nicholas DiPiazza wrote: > Dear group: > > I have a question about the structure of the source code from a cygport > package. > > Here is the contents of a Cygports source file: > > - the actual source bundle for the project (tar.gz, tar.bz2, etc.) > - the any number of *.patch files. > - a .cygport file > > I am trying to build gedit-3.4.2 from cygports repository. > > How does the .cygport file help me run the proper options in the ./configure > ? > > For instance, in gedit if i don't specify --disable-spell it won't proceed > due to error. How do I get the list of ./configure options that were used to > build the project when the cygport was built? > > Or even better, is there some way we can use the cygport executable to build > the cygport with a custom --prefix? > > CYGWIN_NT-6.1-WOW64 w7testpc-PC 1.7.15(0.260/5/3) 2012-05-09 10:25 i686 > Cygwin Downloaded fresh from Cygports today. > > -Nicholas >
the package is using CYGCONF_ARGS="--libexecdir=/usr/lib --enable-python" these are the parameters passed to configure why do you need a custom prefix ? ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Cygwin-ports-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cygwin-ports-general
