Re: [Anjuta-list] Can't add source: Source file must be inside the project directory
- From: Johannes Schmid <johannes schmid gmx de>
- To: Ajit <ajit onmobile com>
- Cc: anjuta-list lists sourceforge net
- Subject: Re: [Anjuta-list] Can't add source: Source file must be inside the project directory
- Date: Thu, 31 Aug 2006 22:43:14 +0200
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Ajit!
Günther Brammer recently send a patch which adds some support for the
constructs you use to gnome-build so you might have success with the CVS
version of gnome-build.
Regards.
Johannes
Ajit wrote:
> Hi Johannes,
>>> This source file restriction is an
>>> automake restriction which can be bypasses by playing around in the
>>> Makefile.am a lot but it is nothing which is desirable.
> Unforunately unavoidable in my case.(compiling cross platform code whose
> directory stucture is already fixed.)
> Any idea how it can be bypassed in makefile.am?
> Regards,
> Ajit
>
> -----Original Message-----
> From: Johannes Schmid [mailto:johannes schmid gmx de]
> Sent: Monday, August 07, 2006 1:31 PM
> To: Ajit
> Cc: anjuta-list lists sourceforge net
> Subject: Re: [Anjuta-list] Can't add source: Source file must be inside
> the project directory
>
>
> Hi!
>
> Anjuta does not implement a full parser for Makefile.am because this is
> not simply possible as autotools were not made with something like this
> in mind.
>
> If you use completly custom Makefiles/Makefile.ams you can do very
> specific stuff but no IDE is able to manage it and maybe not even any
> automake version is able to handle them.
>
> Anjuta is able to import most GNOME CVS modules because they use
> standard automake structures. This source file restriction is an
> automake restriction which can be bypasses by playing around in the
> Makefile.am a lot but it is nothing which is desirable.
>
> Regards,
> Johannes
>
> Ajit wrote:
>>> Hi Johannes,
>>> Note that i get the error:
>>> "Can't add source: Source file must be inside the project directory".
>>> In a popup window from anjutha when adding the file,which leads me to
>>> beleive that its an anjutha error and nothing to do with automake.
>>>
>>> For now i have given up on linux IDEs, due to a lack of
>>> features/restrictions.Have run into this source file restriction in some
>>> other IDEs also.With kdevelop i had issues building static libs.
>>>
>>> Right now its Konsole and manually written make files. :D
>>>
>>> Regards,
>>> Ajit
>>>
>>>
>>> -----Original Message-----
>>> From: Johannes Schmid [mailto:johannes schmid gmx de]
>>> Sent: Sunday, August 06, 2006 3:27 AM
>>> To: Ajit
>>> Cc: anjuta-list lists sourceforge net
>>> Subject: Re: [Anjuta-list] Can't add source: Source file must be inside
>>> the project directory
>>>
>>>
>>> Hi Ajit!
>>>
>>> While I am no real expert but I think you do it the wrong way. Automake
>>> should have a clean way to do what you want and have a Makefile.am in
>>> each directory.
>>>
>>> The project backend of anjuta does nothing more as to add the files to
>>> the correct targets in the Makefile.am of the directory they contain.
>>>
>>> Maybe you should think about building libs in each directory and to link
>>> to them in the top-level build directory. That said, maybe it's a good
>>> idea to check the automake manual.
>>>
>>> Regards,
>>> Johannes
>>>
>>> Ajit wrote:
>>>>> Hi,
>>>>> I am atempting to build (cross platform) c++ projects in anjuta.I
> already
>>>>> have all the cross platform code in a directory structure dvlp/src ,
>>>>> dvlp/inc, dvlp/make(With include source and project files respectively
> in
>>>>> each folder).However when adding existing files from dvlp/src and
> dvlp/inc
>>>>> to the project in dvlp/make i get an error saying "Can't add source:
>>> Source
>>>>> file must be inside the project directory".
>>>>>
>>>>> Is there a way to bypass this error and add the sources using relative
>>> paths
>>>>> ( ../src/file.cpp )??
>>>>>
>>>>> I am unable to reorganize my code structure as the code is already
> being
>>>>> built with this structure on win32 (MSVC) and is checked in to cvs with
>>> this
>>>>> structure.
>>>>> I would like the build output to go into dvlp/bin/linux. (i.e
>>> ../bin/linux
>>>>> wrt to the project file)
>>>>> Regards,
>>>>> Ajit
>>>>> P.S. I am running anjuta 2.0.2
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------
> -
>>>>> Take Surveys. Earn Cash. Influence the Future of IT
>>>>> Join SourceForge.net's Techsay panel and you'll get the chance to share
>>> your
>>>>> opinions on IT & business topics through brief surveys -- and earn cash
>>>>>
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>>>>> _______________________________________________
>>>>> Anjuta-list mailing list
>>>>> Anjuta-list lists sourceforge net
>>>>> https://lists.sourceforge.net/lists/listinfo/anjuta-list
>>>>>
>>>>>
- -------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Anjuta-list mailing list
Anjuta-list lists sourceforge net
https://lists.sourceforge.net/lists/listinfo/anjuta-list
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFE90ni7Dsf+G5b/WsRAoniAKC+Emt6jFtdqgDPS5fqIGcyfLRi2wCgwk/K
PAnm2fX72S05uusRckmkqqw=
=EkG0
-----END PGP SIGNATURE-----
[
Date Prev][Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]