Thanks for your feedback Ian, I don't use VC for my day to day work either, as I mostly develop on Linux. I just gave it a shot after having a lot of linking troubles with the mingw toolset while porting an app to Windows. It was a lot easier for me to track down these two problems in VC than the issues I was having with mingw.
I'm not using VC 6, but VC 2008. Should I try to get a copy of VC 6 and submit patches, or just submit a complete VC 2008 solution / project set? I'll take another look at the mingw tools, as that would be my preference, but I'm still feeling a little nauseous thinking about the hours I spent banging my head against the wall trying (and failing) to get it to work properly. Cheers, Jivan MacArthur, Ian (SELEX GALILEO, UK) wrote: >> These problems have been around for at least a few snapshots now, is >> anyone planning to replace the VC Solution with an updated >> one? If not, >> how can I submit updated files to the project? > > I don't think any of the developers that are active on fltk-2 use the MS > tools for their "day to day" work, so the VC projects may tend to lag > the leading edge... > (Switching to gnu/gcc based tools on Windows works - I use Msys+mingw to > build fltk-2 on WinXP and Vista. Since that uses the basic configure > mechansim, it tracks the leading edge OK and doesn't tend to suffer from > "missed" files.) > > If you have patches, they should be submitted via > > http://www.fltk.org/str.php > > And marked as patches for 2.x for inclusion. > > > > > SELEX Sensors and Airborne Systems Limited > Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 > 3EL > A company registered in England & Wales. Company no. 02426132 > ******************************************************************** > This email and any attachments are confidential to the intended > recipient and may also be privileged. If you are not the intended > recipient please delete it from your system and notify the sender. > You should not copy it or use it for any purpose nor disclose or > distribute its contents to any other person. > ******************************************************************** > _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
