[Insight-developers] Examples in SunOS-5.6-c++ & IRIX-64 : mi ssing FLTK

Miller, James V (CRD) millerjv@crd.ge.com
Mon, 1 Oct 2001 13:01:04 -0400


This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C14A9A.A7ED2480
Content-Type: text/plain

I am building all of these examples from a source tree of FLTK. I am not using any rpms or
preinstalled versions. So Windows, Linux, Solaris, and Irix are all using a source tree of FLTK.

These compile under Windows because windows does not care about case.  The examples build from an
install of FLTK on linux because they are putting in these symbolic links.

The source tree for FLTK has its include directory as FL and its header files end in .H. I suggest
that we use that syntax. 


-----Original Message-----
From: Luis Ibanez [ mailto:ibanez@choroid.cs.unc.edu <mailto:ibanez@choroid.cs.unc.edu> ]
Sent: Monday, October 01, 2001 10:57 AM
To: Miller, James V (CRD)
Cc: insight-Developers
Subject: RE: [Insight-developers] Examples in SunOS-5.6-c++ & IRIX-64 :
missing FLTK





  Well, FLTK people have this problem some time ago
  and they came up with the salomonic decision of creating
  a link directory "Fl" to "FL". The standard distribution of
  FLTK has this link. They also created links with *.H to
  all the *.h files (I confess that this is not very elegant,
  but that's the way it is...)


  The examples are building in Windows and Linux,
  so, this still looks like a path problem in IRIX and SUN
  eventually it could also be problem with the installation
  of FLTK on these machines.

  Any ideas ?


  Luis

------------------------


On Mon, 1 Oct 2001, Miller, James V (CRD) wrote:

> Actually, the problem is not that fltk is missing is that the include lines
> in the examples are wrong.  They are
>
> #include "Fl/something"
>
> and they need to be
>
> #include "FL/something"
>
>




------_=_NextPart_001_01C14A9A.A7ED2480
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE></TITLE>

<META content="MSHTML 5.50.4616.200" name=GENERATOR></HEAD>
<BODY>
<P><FONT size=2>I am building all of these examples from a source tree of FLTK. 
I am not using any rpms or preinstalled versions. So Windows, Linux, Solaris, 
and Irix are all using a source tree of FLTK.</FONT></P>
<P><FONT size=2>These compile under Windows because windows does not care about 
case.&nbsp; The examples build from an install of FLTK on linux because they are 
putting in these symbolic links.</FONT></P>
<DIV><FONT size=2><FONT color=#0000ff>The source tree for FLTK has its include 
directory as FL and its header files end in .H. I suggest that we use that 
syntax. </FONT></DIV>
<P><FONT color=#0000ff></FONT><FONT color=#0000ff></FONT><BR>-----Original 
Message-----<BR>From: Luis Ibanez [<A 
href="mailto:ibanez@choroid.cs.unc.edu">mailto:ibanez@choroid.cs.unc.edu</A>]<BR>Sent: 
Monday, October 01, 2001 10:57 AM<BR>To: Miller, James V (CRD)<BR>Cc: 
insight-Developers<BR>Subject: RE: [Insight-developers] Examples in 
SunOS-5.6-c++ &amp; IRIX-64 :<BR>missing FLTK<BR><BR><BR><BR><BR><BR>&nbsp; 
Well, FLTK people have this problem some time ago<BR>&nbsp; and they came up 
with the salomonic decision of creating<BR>&nbsp; a link directory "Fl" to "FL". 
The standard distribution of<BR>&nbsp; FLTK has this link. They also created 
links with *.H to<BR>&nbsp; all the *.h files (I confess that this is not very 
elegant,<BR>&nbsp; but that's the way it is...)<BR><BR><BR>&nbsp; The examples 
are building in Windows and Linux,<BR>&nbsp; so, this still looks like a path 
problem in IRIX and SUN<BR>&nbsp; eventually it could also be problem with the 
installation<BR>&nbsp; of FLTK on these machines.<BR><BR>&nbsp; Any ideas 
?<BR><BR><BR>&nbsp; Luis<BR><BR>------------------------<BR><BR><BR>On Mon, 1 
Oct 2001, Miller, James V (CRD) wrote:<BR><BR>&gt; Actually, the problem is not 
that fltk is missing is that the include lines<BR>&gt; in the examples are 
wrong.&nbsp; They are<BR>&gt;<BR>&gt; #include "Fl/something"<BR>&gt;<BR>&gt; 
and they need to be<BR>&gt;<BR>&gt; #include 
"FL/something"<BR>&gt;<BR>&gt;<BR><BR></P></FONT></BODY></HTML>

------_=_NextPart_001_01C14A9A.A7ED2480--