STR #1603

FLTK matrix user chat room
(using Element browser app)   FLTK gitter user chat room   GitHub FLTK Project   FLTK News RSS Feed  
  FLTK Apps      FLTK Library      Forums      Links     Login 
 Home  |  Articles & FAQs  |  Bugs & Features  |  Documentation  |  Download  |  Screenshots  ]
 

Return to Bugs & Features | Roadmap 1.1 ]

STR #1603

Application:FLTK Library
Status:1 - Closed w/Resolution
Priority:3 - Moderate, e.g. unable to compile the software
Scope:2 - Specific to an operating system
Subsystem:Build Files
Summary:--enable-threads
Version:1.1.7
Created By:kub
Assigned To:mike
Fix Version:1.1-current (SVN: v5707)
Update Notification:

Receive EMails Don't Receive EMails

Trouble Report Files:


Name/Time/Date Filename/Size top right image
 
#1 kub
05:26 Feb 19, 2007
fltk.spec
11k
 
bottom left image   bottom right image

Trouble Report Comments:


Name/Time/Date Text top right image
 
#1 kub
04:57 Feb 15, 2007
Please include the above option into the spec file.
It is now much work to exchange the preinstalled RPM's
against custom ones.
The affected file is fltk.spec and fltk.spec.in:71 .
 
 
#2 matt
02:11 Feb 19, 2007
I agree, we shoudl make --enable-threads the default and still allow --disable-threads. Or is there something I am missing that may be a disadvantage?  
 
#3 mike
05:05 Feb 19, 2007
The spec file can use --enable-threads and --enable-largefile, just as it uses --enable-shared. The default for a source code compile will remain the same...  
 
#4 kub
05:29 Feb 19, 2007
The distributions, I am faced with dont use custom options. It is much work for a distributor to wade through all the packages to see what works best. So they oviously switch to defaults. The fltk.spec provided options are simply ignored.  
 
#5 mike
04:07 Feb 22, 2007
The spec file has been updated to include --enable-threads and --enable-largefile.

Kai-Uwe: We can't change the defaults in the configure script because that breaks binary compatibility.  As for distributors not spending time to produce good packages, that's not our problem...  The sample spec file will have to be all the guidance we provide...
 
bottom left image   bottom right image

Return to Bugs & Features ]

 
 

Comments are owned by the poster. All other content is copyright 1998-2022 by Bill Spitzak and others. This project is hosted by The FLTK Team. Please report site problems to 'erco@seriss.com'.