FLTK logo

STR #2271

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 2.0 | Post Text | Post File | SVN ⇄ GIT ]

STR #2271

Application:FLTK Library
Status:5 - New
Priority:4 - High, e.g. key functionality not working
Scope:1 - Specific to a machine/printer
Subsystem:Unassigned
Summary:fltk 1.3&2.0 can not build on VC++ 2008 Express
Version:2.0-current
Created By:lonesomesnow
Assigned To:Unassigned
Fix Version:Unassigned
Update Notification:

Receive EMails Don't Receive EMails

Trouble Report Files:

Post File ]

No files


Trouble Report Comments:

Post Text ]
Name/Time/Date Text  
 
#1 lonesomesnow
04:25 Oct 12, 2009
I download fltk-1.3.x-r6879.tar and fltk-2.0.x-r6879.tar and try to build it on VC++ 2008 Express. I open 1.3 and 2.0 visualc/fltk.dsw and try to build it, but it is fail to build successfully. VC++ 2008 Express gives me the following message(fltk2.0).

Can not open 'C:\Documents and Settings\Administrator\桌面\fltk-2.0.x-r6879\ide\visualc\Debug\RSP000001338012
32.rsp'.
...
Can not open '.\Debug\compress.sbr': No such file or directory.
...
'cairo.h': No such file or directory.

Is there any method to solve this problem? I have VC++ 2008 Express only, and I have to work on 2008. Thanks.
 
 
#2 ratulbane
16:11 Apr 29, 2010
I am not able to build any version of fltk on vc++ 2008.My OS is Windows Vista.The following error is being encountered-

LINK : fatal error LNK1181: cannot open input file 'fltk.lib'

someone please suggest something asap
 
 
#3 ratulbane
16:12 Apr 29, 2010
its vc++ professional 2008  
 
#4 ratulbane
16:13 Apr 29, 2010
sorry,rather visual studio professional 2008  
 
#5 mike
09:28 Apr 30, 2010
P3  
 
#6 greg.ercolano
15:24 Apr 30, 2010
> [..] I download fltk-1.3.x-r6879.tar [..]

Hmm, 6879 is a strange SVN rev snapshot for FLTK 1.3.x,
there's been almost 1000 checkins since then.

For 1.3.x, "r7565" is the latest snapshot.. you should probably use that.

Note that 1.3 is still in development. 1.1.10 is the last stable release of FLTK 1.x. (Use 1.3 if you need UTF8, which I'm guessing you do)

The latest SVN of 1.3.x I could find is r7555 which is here:
http://ftp2.easysw.com/pub/fltk/snapshots/fltk-1.3.x-r7555.tar.gz

The following steps worked for me just now with that release in VS 2008 Express:


1) open VS Express

2) Choose Open->Project/Solution, click on the fltk\ide\visualc\fltk.dsw file
   (answer 'Yes to all' for any dialog warning about project conversion)

3) Just below the menu bar, change 'Debug' -> 'Release'

4) Go into Tools -> Options -> Project Solutions -> Build and Run -> and set


4) In the "Solution Explorer" window, scroll to the very top

5) Right click on:
           'fltk' solution (xx projects)
   ..and choose 'Build Solution"

This should (a) build the FLTK libs, and (b) build the example programs
which you can then run.

If that doesn't work, attach your build log as a .txt file,
and we can maybe tell what's up.
 
 
#7 greg.ercolano
15:26 Apr 30, 2010
[oops -- that posted before I was done editing.. dang Tab key moves me off the field to the submit button! Trying again with complete instructions..]


> [..] I download fltk-1.3.x-r6879.tar [..]

Hmm, 6879 is a strange SVN rev snapshot for FLTK 1.3.x,
there's been almost 1000 checkins since then.

For 1.3.x, "r7565" is the latest snapshot.. you should probably use that.

Note that 1.3 is still in development. 1.1.10 is the last stable release of FLTK 1.x. (Use 1.3 if you need UTF8, which I'm guessing you do)

The latest SVN of 1.3.x I could find is r7555 which is here:
http://ftp2.easysw.com/pub/fltk/snapshots/fltk-1.3.x-r7555.tar.gz

The following steps worked for me just now with that release in VS 2008 Express:


1) open VS Express

2) Choose Open->Project/Solution, click on the fltk\ide\visualc\fltk.dsw file
   (answer 'Yes to all' for any dialog warning about project conversion)

3) Just below the menu bar, change 'Debug' -> 'Release'

4) Go into Tools -> Options -> Project Solutions -> Build and Run
   ..and set "maximum number of parallel project builds" to 1.
   (This prevents a parallel build, which is I think the problem)

5) In the "Solution Explorer" window, scroll to the very top

6) Right click on:
           'fltk' solution (xx projects)
   ..and choose 'Build Solution"

This should (a) build the FLTK libs, and (b) build the example programs
which you can then run.

If that doesn't work, attach your build log as a .txt file,
and we can maybe tell what's up.
 
 
#8 greg.ercolano
16:22 Apr 30, 2010
I took the latest fltk-1.3.x (SVN r7575) and compiled it in VS 2008,
but I had to use ide/VisualC6/fltk.dsw to get it to build the libs properly, as the /visualc/ file failed to build fltk.dll and therefore couldn't get very far.

Again, sorry I can't answer to the 2.0 build issue.. 1.x and 2.x are handled by different teams, and the 2.x team is deficient of developers ATM. So I would focus on 1.3.x if you need UTF8.

Even The "VisualC6/fltk.dsw" built the libs OK, but failed to build a few of the test programs, giving these errors:

* * *
------ Build started: Project: mandelbrot, Configuration: Release Win32 ------
Linking...
mandelbrot.obj : error LNK2019: unresolved external symbol "public: void __thiscall Drawing_Window::make_window(void)" (?make_window@Drawing_Window@@QAEXXZ) referenced in function _main
../../test/mandelbrot.exe : fatal error LNK1120: 1 unresolved externals
Build log was saved at "file://\\meade\net\tmp\fltktest\ide\VisualC6\Release\BuildLog.htm"
mandelbrot - 2 error(s), 0 warning(s)
------ Build started: Project: keyboard, Configuration: Release Win32 ------
Linking...
keyboard.obj : error LNK2019: unresolved external symbol "class Fl_Dial * roller_y" (?roller_y@@3PAVFl_Dial@@A) referenced in function "private: virtual int __thiscall MyWindow::handle(int)" (?handle@MyWindow@@EAEHH@Z)
keyboard.obj : error LNK2019: unresolved external symbol "class Fl_Dial * roller_x" (?roller_x@@3PAVFl_Dial@@A) referenced in function "private: virtual int __thiscall MyWindow::handle(int)" (?handle@MyWindow@@EAEHH@Z)
keyboard.obj : error LNK2019: unresolved external symbol "class Fl_Output * text_output" (?text_output@@3PAVFl_Output@@A) referenced in function _main
keyboard.obj : error LNK2019: unresolved external symbol "class Fl_Output * key_output" (?key_output@@3PAVFl_Output@@A) referenced in function _main
keyboard.obj : error LNK2019: unresolved external symbol "class MyWindow * __cdecl make_window(void)" (?make_window@@YAPAVMyWindow@@XZ) referenced in function _main
../../test/keyboard.exe : fatal error LNK1120: 5 unresolved externals
Build log was saved at "file://\\meade\net\tmp\fltktest\ide\VisualC6\Release\BuildLog.htm"
keyboard - 6 error(s), 0 warning(s)
------ Build started: Project: CubeView, Configuration: Release Win32 ------
Linking...
CubeMain.obj : error LNK2019: unresolved external symbol "public: void __thiscall CubeViewUI::show(int,char * *)" (?show@CubeViewUI@@QAEXHPAPAD@Z) referenced in function _main
CubeMain.obj : error LNK2019: unresolved external symbol "public: __thiscall CubeViewUI::CubeViewUI(void)" (??0CubeViewUI@@QAE@XZ) referenced in function _main
../../test/CubeView.exe : fatal error LNK1120: 2 unresolved externals
Build log was saved at "file://\\meade\net\tmp\fltktest\ide\VisualC6\Release\BuildLog.htm"
CubeView - 3 error(s), 0 warning(s)
========== Build: 0 succeeded, 3 failed, 80 up-to-date, 0 skipped ==========
* * *

..looks like some simple dependencies have been missed in those project.

Upping the priority to '4' to hold up 1.3.x's release, as we should not release 1.3 without 100% build in VS2008.
 
 
#9 greg.ercolano
18:27 Apr 30, 2010
I just did a /clean/ checkout of 1.3.x r7575, and it compiled OK in VS 2008 with no errors. I must have had a crufty r7575 to get those errors
from my last try.

Steps to build were successfully with r7575:

    1) open VS Express 2008

    2) Choose Open -> Project/Solution,
       click on fltk\ide\Visualc6\fltk.dsw file,
      (answer 'Yes to all' for project conversion warning)

    3) Just below the menu bar, change 'Debug' -> 'Release'

    4) Go into:
       Tools -> Options -> Project Solutions -> Build and Run
       ..and set "maximum number of parallel project builds" to 1.
      (prevents a parallel build)

    5) In the "Solution Explorer" window, scroll to the very top

    6) Right click on:
           'fltk' solution (xx projects)
       ..and choose 'Build Solution"

Builds all 83 projects, no errors. (151 warnings)

But if I skip step #4 (and leave it do a parallel build with '2'),
then the build definitely fails, because it tries to build the test programs while the fltk.lib is still being built.

So we have something wrong with parallel builds, I'm almost positive about that.

Attach your complete build log history as a .txt if that doesn't work.
 
 
#10 matt
23:41 Apr 30, 2010
The parallel build issue is a known issue with VisualC. It's a Microsoft issue and has caused a lot of complaints because it does not work with projects that are created "manually".

Unfortunately I can't fix the VisualC6 setup to disable the parallel build because that flag did not exist back then.
 
 
#11 greg.ercolano
08:28 May 01, 2010
Matt: don't worry -- I think I found the fix.
Simple search/replace to change the "Intermediate Directory"
setting in all the *.dsp files. See:
http://fltk.org/newsgroups.php?gfltk.development+v:10295

..which describes the problem, solution, and the perl script to do the change. I'd like to check these changes in if you think they seem sane.
 
 
#12 greg.ercolano
17:06 May 12, 2010
Looks like Matt fixed this in 1.3.x r7583;
all the dsp files and the fluid ide_visualc.cxx file.

Leaving this open for FLTK 2.x developers to follow up.
 
     

Return to Bugs & Features | Post Text | Post File ]

 
 

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