Test/Check Request: Openshot 1.4.1 (Update)

[Archie]

Thanks, TerryN. Renamed ~/.openshot & added #!/bin/sh in /usr/bin/blender and all is well again  

I've been meaning to ask about this ... OK I'm a bit daft and I should just first try it but this is bugging me. /usr/bin/blender is a binary file. I'm sure it can be edited with a text editor.

When you mean add #! /bin/sh at the top of the file, did you mean it literally? Wouldn't that mess up the blender (the executable)? Wouldn't it be the same as calling the executable with a bash script that included #! /bin/bash?

Just curious.

No, it is not a binary executable it is a shell script wrapper!    
And you are right Archie, editing a binary file will corrupt the same.  
BTW, the real executables are /usr/bin/blender.sse and /usr/bin/blender.nonsse, the shell script wrapper select one or the other depending if the CPU support sse or not.

Thanks for the explanation, AS. I would have thought it was the binary when I opened it (I can't remember how long ago) and saw nothing but jibberish text, symbols and numbers.

Are the devs at Blender aware of this workaround with Openshot? I guess the Openshot devs already know about this.

Anyway, I learned something new again today ... shell script wrapper ... and it don't look anything like a shell script. 

[TerryN]

Are the devs at Blender aware of this workaround with Openshot? I guess the Openshot devs already know about this.

It's actually OUR spec file that creates the wrapper 

Terry.

[AS]

Thanks, TerryN. Renamed ~/.openshot & added #!/bin/sh in /usr/bin/blender and all is well again  

I've been meaning to ask about this ... OK I'm a bit daft and I should just first try it but this is bugging me. /usr/bin/blender is a binary file. I'm sure it can be edited with a text editor.

When you mean add #! /bin/sh at the top of the file, did you mean it literally? Wouldn't that mess up the blender (the executable)? Wouldn't it be the same as calling the executable with a bash script that included #! /bin/bash?

Just curious.

No, it is not a binary executable it is a shell script wrapper!    
And you are right Archie, editing a binary file will corrupt the same.  
BTW, the real executables are /usr/bin/blender.sse and /usr/bin/blender.nonsse, the shell script wrapper select one or the other depending if the CPU support sse or not.

Thanks for the explanation, AS. I would have thought it was the binary when I opened it (I can't remember how long ago) and saw nothing but jibberish text, symbols and numbers.

Are the devs at Blender aware of this workaround with Openshot? I guess the Openshot devs already know about this.

Anyway, I learned something new again today ... shell script wrapper ... and it don't look anything like a shell script. 

There could be some misunderstanding here, /usr/bin/blender actually is a 10 lines or so text file... no jibberish inside. 

[Archie]

There could be some misunderstanding here, /usr/bin/blender actually is a 10 lines or so text file... no jibberish inside. 

There certainly is one now. Out of curiosity I installed it and opened it with Kwrite ... 98908 lines, AS.



What's going on here? 

[AS]

blender 32bit here: blender-2.60a-1pclos2011, (reinstalled right now).

# cat /usr/bin/blender
if [ -e /proc/cpuinfo ]; then
        SSE="`cat /proc/cpuinfo | grep flags | grep sse`"
fi

if [ "x$SSE" == x ]; then
        /usr/bin/blender.nonsse "$@"
else
        /usr/bin/blender.sse "$@"
fi

[TerryN]

Archie is looking at the 64bit version.  There is no "non-sse build" on 64 bit and therefore no need for the wrapper.

Terry

[AS]

Archie is looking at the 64bit version.  There is no "non-sse build" on 64 bit and therefore no need for the wrapper.

Terry

Fair enough! 
My answer was primarily related to "editing a binary file", clearly coffeetime applied the changes to the 32bit version.

AS

[TerryN]

No problem 

It's all my fault as I should have said that in my original post.  I'll go and edit it now .... 

Terry

[Archie]

Whew! I thought I learned something, and I did.

AS, my query was from the original post that gave instructions on editing /usr/bin/blender. It also didn't occur to me that this was only specific to i586.