View Single Post
Old 07-25-2018, 09:24 PM   #5
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by txwindsurfer View Post
I just now found the "culprit". I just delete the CALIBRE_DEVELOP_FROM environment variable I had set last week, and now the server starts. And no error.
I'm not sure how that was causing the issue and if anyone can explain I'd appreciate it. I had the variable set under System Properties > Environment Variables > System Variables
That environment variable is used when you want to run calibre from source. It points to where the source code is. If the needed source files are not in that location, then calibre will fail.

For development, I don't set the environment variable globally. I use a batch wrapper script that does the setup needed and starts calibre-debug. That way I can run different versions if needed or the released code with no changes.
davidfor is offline   Reply With Quote