Ticket #65 (assigned defect)

Opened 2 years ago

Last modified 1 month ago

scons unit-tests don't work

Reported by: vossg Assigned to: allenb (accepted)
Priority: observe Milestone: 2.0 Beta
Component: Build Version: 2.0
Keywords: Cc:
Completion:

Description (Last modified by marcusl)

I still can not build OpenSG 2.x on windows using scons, something

goes wrong while creating osg-config. Log file attached. Note

there are some debug prints in there just ignore the

Key … Value … stuff.

Attachments

scons_broken.log (13.2 kB) - added by vossg on 09/25/06 21:16:46.
option.cache.win32 (497 bytes) - added by vossg on 10/02/06 21:19:43.

Change History

09/25/06 21:16:46 changed by vossg

  • attachment scons_broken.log added.

(in reply to: ↑ description ) 09/25/06 21:21:16 changed by vossg

  • description changed.
  • milestone set to 2.0 Beta.

Replying to vossg:

I still can not build OpenSG 2.x using scons, something goes wrong while

creating osg-config. Log file attached

09/26/06 17:59:36 changed by allenb

  • owner changed from unassigned to anonymous.
  • priority changed from critical to blocker.
  • status changed from new to assigned.

The windows build is doing better now. I fixed up a number of corner cases for the build and it runs much further. It is now failing on a symbol problem with one of the texture files. I will try to track it down, but I have limited time. If anyone else have time to look at this, the help would be greatly appreciated.

10/01/06 15:22:15 changed by allenb

  • owner changed from anonymous to allenb.
  • status changed from assigned to new.

The windows build should work now. As soon as we get confirmation that it works for 2 different people I think this ticket can be closed.

10/01/06 19:09:41 changed by dirk

I tried but couldn't get it to work.

  • scons 0.96.92 is broken for MSVC 8 (missing os.path.join, easy to fix)
  • somehow my framework dir is ignored, so it can't find windows.h. Could be my hosed installation (too many partial versions of MSVC…).

Had to give up at that point, need to revisit when I have more time.

(follow-up: ↓ 6 ) 10/01/06 21:25:43 changed by vossg

Me neither it still throws an exception while processing osg-config. Not a single

file is build.

gerrit

(in reply to: ↑ 5 ) 10/02/06 08:02:01 changed by allenb

Replying to vossg:

Me neither it still throws an exception while processing osg-config. Not a single

file is build.

gerrit

Does it still through the same exception as in the log above?

-Allen

(follow-up: ↓ 8 ) 10/02/06 09:36:55 changed by vossg

yes, reinstalling cygwin did not help. Running it directly from a dosbox (to make sure it is

not some strange cygwin influence) did not help either.

(in reply to: ↑ 7 ) 10/02/06 09:51:28 changed by anonymous

  • owner changed from allenb to anonymous.
  • status changed from new to assigned.

Replying to vossg:

yes, reinstalling cygwin did not help. Running it directly from a dosbox (to make sure it is

not some strange cygwin influence) did not help either.

What version of python are you using?

It is likely that the build will fail if using cygwin in any way including using the cygwin python.

I am currently using Python 2.5 from python.org and running inside a dos shell.

-A

10/02/06 09:51:58 changed by allenb

  • owner changed from anonymous to allenb.
  • status changed from assigned to new.

10/02/06 10:02:27 changed by vossg

IIRC 2.4 (machine is in office). I can try 2.5 tomorrow and see if there is any change.

(follow-up: ↓ 13 ) 10/02/06 20:47:01 changed by vossg

even less successful : 



gerrit@rutherford:OpenSG% /c/Python25/scons.bat

scons: Reading SConscript files ...

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

WARNING: The build is currently in development.

            - It needs the svn version of scons-addons

WARNING:

  File "Tools\scons-addons\src\SConsAddons\Util.py", line 30



    from __future__ import generators



SyntaxError: from __future__ imports must occur at the beginning of the file

10/02/06 20:57:08 changed by dirk

Yup, seen that. Trivial fix: move the future one line up.

(in reply to: ↑ 11 ) 10/02/06 21:00:12 changed by allenb

Replying to vossg:

even less successful :

{{{

gerrit@rutherford:OpenSG% /c/Python25/scons.bat

scons: Reading SConscript files …

————————————————————————-

WARNING: The build is currently in development.

- It needs the svn version of scons-addons

WARNING:

File "Tools\scons-addons\src\SConsAddons\Util.py", line 30

from future import generators

SyntaxError?: from future imports must occur at the beginning of the file

}}}

I doubled checked. I am using Python 2.4 from a dos shell. I don't have cygwin or anything similar in my path.

The error you are seeing is very strange. I have not seen anything like that on any platform. Can you think of anything abnormal about your system setup or the options you are using with SCons? I am at a loss to come up with any idea. :(

(follow-up: ↓ 15 ) 10/02/06 21:19:10 changed by vossg

1) moving future helped a little bit, not the old exception while

generating osg-config is back.

2) I tried both cygwin and a dos shell, same result.

Everything relevant is a fresh install (cygwin/OpenSG/Python/scons)

Besides boost I don't use any option (option cache attached)

3) BTW BoostIncludeDir does not work.

10/02/06 21:19:43 changed by vossg

  • attachment option.cache.win32 added.

(in reply to: ↑ 14 ) 10/02/06 22:35:45 changed by allenb

  • status changed from new to assigned.

Replying to vossg:

1) moving future helped a little bit, not the old exception while

generating osg-config is back.

2) I tried both cygwin and a dos shell, same result.

Everything relevant is a fresh install (cygwin/OpenSG/Python/scons)

Besides boost I don't use any option (option cache attached)

That sounds like a good setup to me. I wish I could replicate the problem shown in your log. I have tried the build on several windows setups now and I haven't run into that problem. I will see if I can think of anything else tomorrow.

3) BTW BoostIncludeDir does not work.

That is strange. We have been using it for quite a few other projects. Once we get the osg-config issue tracked down we should get to the bottom of this as well.

12/04/06 21:13:22 changed by dex

  • estimated_completion changed.

01/15/07 02:34:09 changed by vossg

Hi,

just tried again, and after a little bit SContruct tweaking it seems to work. At least the

exception is gone and the osg-config are there. Let's see what happens.

I change it to minor and keep an eye on it.

Could we add something like 'observe' as a potential priority selection ?

gerrit

01/15/07 02:36:05 changed by vossg

  • priority changed from blocker to minor.

01/15/07 12:22:20 changed by dirk

  • priority changed from minor to observe.

Observe: done. Set above trivial below minor.

01/15/07 20:56:11 changed by vossg

first observation : the unit tests don't build, will have a look

gerrit

01/16/07 08:22:05 changed by dirk

Note: the unit tests don't build on any platform right now due to missing Fixed functionality. Different story. But the normal test programs don't build either, which IMHO they shouldn't (#152).

The /nodefaultlib seems to be a problem there, a lot of system stuff is missing.

12/02/08 09:01:19 changed by marcusl

  • description changed.
  • summary changed from scons broken on windows to scons unit-tests don't work.

Changed title to something less alarming and more true. (was: scons broken on windows)

12/04/08 06:35:48 changed by marcusl

Actually, the tests do build? If the unit-test are all the little testFoo-exes?

Close this?