[haiku-3rdparty-dev] Re: Get the Application's Working Directory
- From: Pasquale Rinaldi <pjrinaldi@xxxxxxxxx>
- To: haiku-3rdparty-dev@xxxxxxxxxxxxx
- Date: Thu, 12 Aug 2010 22:33:30 -0400
Okay,
A question for darkwyrm. I installed recibe with sources to look at
the cppsqlite3 wrapper. I compiled my app to check out something and
now I am getting:
/HaikuData/Projects/masterpiece/(Objects.MasterPiece)/MainWindow.o: In
function `MainWindow::MainWindow(void)':
/HaikuData/Projects/masterpiece/MainWindow.cpp:35: undefined reference
to `sqlite3_open_v2'
collect2: ld returned 1 exit status
Could this be related to installing recibe which might have
overwriiten the original sqlite library/header stuff?
i saw online how undefined reference usually refers to library linking
issues, but the other sqlite commands still work without bringing up
errors. I was using sql_open_v2 so that if the db doesn't exist, i
could create it in code with the table structure...
I'm not sure if that's a coincidence or i'm just missing something.
Thanks for the help,
Pasquale
On 8/12/10, Pasquale Rinaldi <pjrinaldi@xxxxxxxxx> wrote:
> Thanks to everyone for the helpful info and suggestions. I've applied
> darkwyrms solution and am researching the other information to ensure
> my app will be future proof. Thanks again for the quick responses.
> Another great feature of haiku.
>
> On 8/12/10, Axel Dörfler <axeld@xxxxxxxxxxxxxxxx> wrote:
>> Stephan Assmus <superstippi@xxxxxx> wrote:
>>> On 2010-08-12 at 13:42:47 [+0200], Pasquale Rinaldi
>>> <pjrinaldi@xxxxxxxxx>
>>> > wrote:
>>> > I've looked through all the documentation and can't find a way to
>>> > determine
>>> > the apps starting directory. Is there a way to do this in Haiku?
>>> > If its in
>>> > the documentation, I either was looking up the wrong information.
>>> > Here's
>>> > what I'm trying to do:
>>> >
>>> > My app uses a sqlite db that is in the directory of the
>>> > application, and I'd
>>> > like to not have to hard code its location into my code. Or, better
>>> > yet, if
>>> > I could make it a resource or somehow embed it, then I wouldn't
>>> > have to deal
>>> > with whether its location is properly defined.
>>> Others have provided a direct answer to your question. I'd just like
>>> to add
>>> that to make your application future proof for multi-user Haiku
>>> setups, it's
>>> probably a better idea to locate dynamic data in the users settings
>>> folder.
>>
>> Or better, use find_directory() with B_USER_DATA_DIRECTORY (data, not
>> settings).
>>
>> Bye,
>> Axel.
>>
>>
>>
>
Other related posts:
