Freestyle integration into Blender

September 9, 2008

Freestyle branch (finally) builds on Windows

Filed under: Update — The dev team @ 7:06 PM

Thanks to Nathan Letwory (jesterking), the Win32 build is now a reality ! Nathan and I were able to hunt down the last remaining problems:

  • Freestyle was originally using extgl in its Windows version to determine if glBlendEquation is made available by the graphic card’s driver. Thanks to Apricot, glew was incorporated into Blender a few months ago. I used it to test for glBlendEquation‘s presence.
  • The original SConscript file for the Win32 build was somewhat buggy and would not compile the files in the rendering folder.
  • Custom Python searchpaths provided by Freestyle (used to import style modules) would not be recognized by the Python interpreter due to format inconsistencies (Blender’s file functions would use a single forward slash for directory separators, while Windows require double backslashes). Nathan normalized the paths by adding the ‘r’ prefix to each pathname.

The latest revision (16442) can be used to produce a fully-working Win32 build (do not forget to define the system environment variable FREESTYLE_BLENDER_DIR, containing the full path to the source/blender/freestyle folder). I encourage you all to make a build a share it on graphicall.

2 Comments »

  1. nice, i’m looking forward to a new OSX build, and linux build, but I’m sure many will be pleased to have the win32 build working.

    Comment by 3D — September 9, 2008 @ 11:37 PM

  2. Currently, it seems that it does not treate FREESTYLE_BLENDER_DIR environment variable and style files very well on windows and linux due to directory separators.

    I hope I can contribute to it in python aspect.

    1.you said “Custom Python searchpaths provided by Freestyle (used to import style modules) would not be recognized by the Python interpreter due to format inconsistencies (Blender’s file functions would use a single forward slash for directory separators, while Windows require double backslashes). Nathan normalized the paths by adding the ‘r’ prefix to each pathname.”

    In fact, both ‘\’ and ‘/’ can be used for directory separators in the following cases
    a). sys.path.append(‘c:/something’), sys.path.append(r’c:\something’) and sys.path.append(‘c:\\something’) have the same effect

    b). if a parameter for a python function is a filename, then somefunction(‘c:/something/a.txt’), somefunction(r’c:\something\a.txt’) and somefunction(‘c:\\something\\a.txt’), have the same effect

    2.if you do need to know the current native directory separators, you can use os.path.sep

    Comment by oyster — September 22, 2008 @ 12:47 PM


RSS feed for comments on this post. TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Create a free website or blog at WordPress.com.

%d bloggers like this: