Today I change branch in local and make up-date and “make release” for 2.83 branch. But I can not run blender 2.83 , it show system erroer message “can not find tbb.dll”
There are tbbmalloc.dll and tbbmalloc_proxy.dll in build release directory.
Do I really need tbb.dll to run current 2.83 branch ?
I could run 2.9 (master), and 2.82 branch without problem. and about those 2
build directory, there seems no tbb.dll eather.
======
I found tbb.dll in blender-git\lib\win64_vc15\tbb\lib
so I just copy and paste it. then now I can run exe.
. (so it seems up-date correctly, and when I make build
git show no erroer, Though I do not know, why not copy the tbb.dll in build directory,when I “make update”
As I have mentioned, After I change git branch from master to blender283
(which I assgin branch name for 2.83 release blanch), I actually did make update , to up-date . To get recent build. then build by “make release”
And about 2.90 and 2.82 which I mentioned, I have not up-dated for several weeks. just test them if I could run . (so my current 2.90 have no tbb.dll in exe directory)
the above 2.90 exe can run blender.exe, without erroer.
So I think it is strange. because I “make update” after exchange branch to 2.83
there is no possibility I forgot it. (Yesterday, I only did make up-date , one -time.
after change blance283.
(usually I change branch for 2.90 ,2.83, sometimes 2.82, and make up-date
about all branch)
And the problem happened, when I click, (or use command prompt), to run
2.83 blender exe.
Then I suppose, recent version 2.83 seems use tbb.dll
and the tbb.dll which I copied is for 2.83 too , is not it?
I retry again. but I confirm, when I use “make update” in local 2.83 branch,
then “make release”, it remove tbb.dll from build blender.exe directory… Then I return same error “there is no tbb.dll” when I run the blender.exe (2,83 release)
I hope if you can confirm it. (though I have already copy version, which I built and move the tbb.dll to the exe directory)
try running cmake . in your build folder after running make udpate , include the . it’s important. also i can’t stress this enough, do NOT run this in the blender source folder, it will do bad things, it needs to be the build folder (ie build_windows_blahblahblah_Release)
Thanks, now I try change branch to master, and " make update" for master.once.
After that change branch, tol blender2.83>make update>make release (<<current)
if it still not work, (will not install tbb.dll in bin\release,) I will follow your guide thanks
If you are using a custom branch name like blender283 instead of blender-v2.83-release then indeed make update will not recognize it. You must use the same branch name as on the git sever, which is blender-v2.83-release.
, actually after I made git repository for master (current 2.90) (follow blender wiki)
I did
git checkout -b blurblurblur origin/blender-v2.83-release
then I did same thing ,for v2.82
Then usually I exchange local branch >>make update >>make release
these procedure is wrong?
So if it not work,(I did not know much about git,) how I can keep branches,
and up-date easy? I can not set local branch name, to get remote branch to up-date? or I only need to use pefrectly same branch name(remote)
git checkout -b blender-v2.83-release origin/blender-v2.83-release
will work?
(then git checkout blender-v2.83-release ,when I change local branch,)
Thanks so you and brecht seems advice same thing,
(but you offer way to keep current local branches)
then I will try your way to confirm, but I will need the step
(svn switch (link lib)) everytime, when I exchange local git (as original name)?
if so I will remake aagain, to use remote-name,or I suppose if I should not make
local branch, but checkout from remote every time,
OK, I seems need to test and understand myself, thanks yours take time to tach coarrect way.
make update may or may not switch you to a different set of SVN libraries, so when you use that, you need to validate manually with svn info you are on the right branch for what you are building.
make code_update will not touch the svn libraries (but you have to manually select the libs you want, once. or whenever you switch brances)
I see, but it seems beyond my memory, (just hope to keep up-date 2 branch and master, )
So I now delete my name local branches, and make local as remote name.
as brecht taught me.
(just use git checkout blender-v2.83-release without -b option,)
after all it seems checkout remote local, and make new local branch but use same branch name as remote.
. (though I do not like everytime check local branch name, to checkout)
hope it work… (if not I test svn method what you mentioned,) anyway thanks you make things clear for me.
without assgin original branch name with -b option.
then make up-date and make release. and run exe it run without erroer.
And I could confirm, in exe directory, there is no tbb.dll still.
So current 2.83 seems no need to install tbb.dll (which I see erroer message, before)