I appear to continue having problems updating from the git.
Would somebody please give me an appropriate script that I can use.
Thanks;
David
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM
Written from memory but should work:
""" CUT HERE
#!/bin/sh
rm -fr build
rm -fr /opt/darktable/*
git pull upstream master
./build.sh --prefix /opt/darktable --buildtype Release
cd build
make install
""" CUT HERE
For the second line to work you must be the owner of /opt/darktable/
(sudo chown -R
Hello,
Using Darktable 2.0.1 on mac.
I experiment some crashes using drawn masks and stain removal tool.
When trying to remove a small stain inside a nose I had a very strange
behavior, Darktable freezed and the area duplicated was totally different
than the selection. I managed to replicate the
Am Freitag, 19. Februar 2016, 09:10:23 schrieb Pedro Côrte-Real:
[...]
> rm -fr build
> rm -fr /opt/darktable/*
Why do people do this? It's making the whole idea of using something like
"make" pointless. You ONLY have to delete things if a build fails because of
cached CMake results.
> git pu
On Fri, Feb 19, 2016 at 10:02 PM, Tobias Ellinghaus wrote:
>> rm -fr build
>> rm -fr /opt/darktable/*
>
> Why do people do this? It's making the whole idea of using something like
> "make" pointless. You ONLY have to delete things if a build fails because of
> cached CMake results.
That's not tru
So I ran:
--
cd /opt/darktable
git pull
cd build/
make -j install
---
and I got the following error message
--
Install the project...
-- Install configuration: "Release"
-- Up-to-date: /opt/darktable/share/locale/cs/LC_MESSAGES/darktable.mo
CMake Error at po/cmake_install.cmake:44 (fi
On Fri, Feb 19, 2016 at 10:22 PM, David Vincent-Jones
wrote:
> So I ran:
> --
> cd /opt/darktable
/opt/darktable should be your install dir. Your git clone should be
somewhere else. Maybe /home/youruser/darktable/ or something like
that. That's where you're supposed to be running all the comm
It also looks like you do not have permissions to create files inside
/opt/darktable. That will become a problem when you attempt to run make
install, so you should follow Pedro's earlier suggestion as well and give
your user permissions to write in /opt/darktable:
sudo chown -R youruser /opt/dark
Am Freitag, 19. Februar 2016, 22:11:17 schrieb Pedro Côrte-Real:
> On Fri, Feb 19, 2016 at 10:02 PM, Tobias Ellinghaus wrote:
> >> rm -fr build
> >> rm -fr /opt/darktable/*
> >
> > Why do people do this? It's making the whole idea of using something like
> > "make" pointless. You ONLY have to del
On Fri, Feb 19, 2016 at 10:56 PM, Tobias Ellinghaus wrote:
> Well, we had that, but the problem wasn't old .so in the install directory but
> that someone removed a module without bumping the api version. If that was
> done (I did it later to fix the problems) then the left over woud just be
> ign
I am running a fairly 'basic' Debian where the current dt version is
prior to 2.0
I have some years back pulled from git on a regular basis without problems.
I guess I will just run this again from the start and make sure to run
from my home dir.
David
On 19/02/16 11:59 PM, Pedro Côrte-Real wr
On Fri, Feb 19, 2016 at 11:04 PM, David Vincent-Jones
wrote:
> I am running a fairly 'basic' Debian where the current dt version is prior
> to 2.0
> I have some years back pulled from git on a regular basis without problems.
In that case I'd suggest you just grab a release tarball (2.0.1 right
no
Thanks ... will do
David
On 20/02/16 12:09 AM, Pedro Côrte-Real wrote:
> On Fri, Feb 19, 2016 at 11:04 PM, David Vincent-Jones
> wrote:
>> I am running a fairly 'basic' Debian where the current dt version is prior
>> to 2.0
>> I have some years back pulled from git on a regular basis without pro
13 matches
Mail list logo
