Xcode4.1 build path (Library/Developer/Xcode/DerivedData)

Hello, after installing Lion and upgrading to Xcode4.1: opened the project from 10.6.7 (Xcode3.2.2) , made some adjustments, builds ok, but:
build path is always: Users/user1/Library/Developer/Xcode/DerivedData/... How I can change to my output location which is in other place (project relative)
Thanks.

I have various data relative to the application, which need to be read/write during run, and this data is relative to the App. location.

Similar Messages

Library Build Path + Interfaces

New interfaces created within a Flex Library project (using Flex Builder 3 or Flash Builder 4) are not automatically added to the project build path in the same way classes are. Is that a design feature (expected behaviour) or is it a bug? It seems a bit strange, to me at least, that interfaces need to be added to the build path manually.

You're right, this is a bug. I have logged it here: http://bugs.adobe.com/jira/browse/FB-20407
Thanks for mentioning it.

Including Library in Build Path

I am using Eclipse 3.x,
How do I add External Libraries in my Project
Ans: Add all the external Jars in the build path (from project properites)
What if its a huge hirarchy ?
Ans shoud be: make a userlibrary and link that library to the folder which contains all jar files (hirarch of folders), and then include that userlibrary to your project.
Problem; If I create userlibrary, I have to select the jar files .. not the higetst level folder, which contains all the jar files ... This is what I dont want. I want to just select a folder.. and that all, and then use this folder as the build path .. "HOW do I do this ""??
-

In eclpise, Drop all jar files under the lib folder of your project (including folders and subfolders).
Right click on the project icon, go to <properties><java build path><libraries>
Navigate to one of the sub folders. click on the top jar file, hold down the <shift> key and then click on the bottom jar file. All jar files between are selected. Add them to the project. Since this is a one-time-only effort, I wouldn't spend too much time trying to find a better short cut. You can pretty quickly go though each subfolder and get what you need.
If you insist on your way, perhaps you need to repackage all the folders and subfolders with thier jar file in an all enclosing jar file with a manifest. I dont know how to do this.
An alternative is to read up on Maven (the more modern way of automatically adding jar files and thier correct versions to a project). However, it will probably take you a long time to come up to speed on it.

How to create a static library using xcode ?

Hi,
I need to create a C static library using xcode in order to use it in another developement environment which is Free Pascal Compiler/Lazarus.
I have very few knowledge about C. I just know how to program the function I need and I've already written my C function using xcode.
Using Lazarus (Pascal IDE), for example, as I use IOKit, I have declared the path of IOKit in the linking section (that is /Developer/SDKs/MacOSX10.6.sdk/System/Library/Frameworks/IOKit.framework/IOkit) . IOKit is a unix executable, and I can use the exported functions it contains in my Pascal code.
So, I would build such kind of unix executable where I can put my own functions written in C. But I can't figure out how to do it.
How to export my functions ? Must I use some specific C keywords to "publish" them (export, __export,...) ? How to create an executable file like IOKit ? Which kind of project must I choose in XCode ?...
André.
Message was edited by: sinfoni12345
Message was edited by: sinfoni12345

Thanks for the response. Yes, that's how I started. I have now managed to get it to build static libraries; the piece I was missing was the scheme stuff. I also tried to build dynamic libraries, but still no luck with those. It was a little confusing because sometimes if I started a new project the scheme would allow me to create output as is; other times I had to edit the scheme first. So reading the documentation appears to have paid off after all.
FWIW, what I was trying to build was a missing library needed for a project in Python. The entire project has two C libraries, which I've managed to build now, altough I don't know if there are some specific options that I need to set for them to work with the C wrapper. The C wrapper is written in Cython, which creates a C file from Python-like statements. The end result of linking the two libraries and the compiled C wrapper should be a file that can be imported into Python, which should have an extension of ".so".
So far the last part is not working, so I don't know if the problem is with the build settings for the libraries, or something else.

Creating a static library with XCode cross-project references.

I have a project and am trying to move a lot of the code into a static shared library, and added a cross project reference to this library in my app.
However, when I moved a file from my app to the library (removing the reference in my app and moving the file to the library's project directory), and try building my app, I get compiler error messages as if the file I have moved doesn't exist.
When I build my library project, it says the build has succeeded, but the library.a file remains red. It is also red in the my referencing app project.
If anybody has any experience setting up cross-project references in XCode, I'd appreciate any help.
If it helps identify where the problem is, I've performed the following steps to setup the library and cross-project reference:
1. I created a new Cocoa Touch static library project in XCode which would house the shared code.
2. I changed the global settings in XCode to place the build products in a shared build directory (rather that the project directory), and made sure the intermediate build files are placed with the build products.
I changed this using the Preferences menu, but have also gone into the project info for both my app project and the library project and made made sure it is set to place the build projects in the custom shared build directory.
3. I then added a Source Tree, and made sure that the Path of the project directory of the library project.
4. I added a project reference to the library project's .xcodeproj file in my application project. I changed the library project reference so that it was relative to JIGSAW24LIBRARY.
5. I configured the library dependencies by going to my app's target's info, and adding a direct dependency to the library project.
6. In my app's info build tab, I changed the user header search paths so that it uses the search tree I setup (I used the $(SEARCHTREE_NAME) notation, but checked that this resolves to a valid path). I also made sure that the Always Search User Paths checkbox is checked, and that the Library Search Paths is blank.
7. I click-dragged the library.a file under the library project so that it was under the Link Binary With Library sub folder of my app's target.
For step 5, I've also tried adding the reference to the other project as a linked library, rather than a direct dependency, but this doesn't seem to work either.

I managed to fix the problem. The steps above seem to be correct. The problem seems to be related to the source trees that are defined...
I was previously using an absolute path for the source tree which pointed at the folder containing the library project. I changed this to a relative path to the same folder (relative from the calling project) and this seems to fix it.
I'd double checked that the absolute path specified was correct, so it looks like the user header search paths specified must be relative to the current project.

Command Line Tools installs the latest version of clang (and others) in /Library/Developer/CommandLineTools/... but not in /usr/bin/

I've upgraded Xcode to the latest 5.1 Installed Command Line Tools via xcode-select --install Homebrew tells me "A newer Command Line Tools release is available"
brew --config:
Xcode: 5.1 CLT: 5.1.0.0.1.1393561416 LLVM-GCC: build 2336 Clang: 3.1 build 318
Checking my clang executable:
$ /usr/bin/clang --version Apple clang version 3.1 (tags/Apple/clang-318.0.58) (based on LLVM 3.1svn)
$ /Library/Developer/CommandLineTools/usr/bin/clang --version Apple LLVM version 5.1 (clang-503.0.38) (based on LLVM 3.4svn)
So it appears Command Line Tools didn't install clang (and perhaps other executables) into /usr/bin? I checked my other laptop (w/ Mavericks), and /usr/bin/clang is version 5.1.
So I'm guessing this is the problem? I've tried to reinstall Command Line Tools as sudo, but now it won't let me install again (says software isn't currently available).
Can anyone help me with this? I've spent hours on it now, but can't find a solution.
Thanks

BTW, I installed Xcode 5.1 from the Store, but have never run xcode-select --install. Here is the verbose output from a clang.
xew ~/$:clang -v -o hello main.c
Apple LLVM version 5.1 (clang-503.0.38) (based on LLVM 3.4svn)
Target: x86_64-apple-darwin13.1.0
Thread model: posix
"/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain /usr/bin/clang" -cc1 -triple x86_64-apple-macosx10.9.0 -emit-obj -mrelax-all -disable-free -disable-llvm-verifier -main-file-name main.c -mrelocation-model pic -pic-level 2 -mdisable-fp-elim -masm-verbose -munwind-tables -target-cpu core2 -target-linker-version 236.3 -v -resource-dir /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/ usr/bin/../lib/clang/5.1 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/ SDKs/MacOSX10.9.sdk -fdebug-compilation-dir /Users/xew -ferror-limit 19 -fmessage-length 100 -stack-protector 1 -mstackrealign -fblocks -fobjc-runtime=macosx-10.9.0 -fencode-extended-block-signature -fdiagnostics-show-option -fcolor-diagnostics -vectorize-slp -o /var/folders/zf/d5vqmmtn5mq7h6766jtlkrvr0000gn/T/main-353995.o -x c main.c
clang -cc1 version 5.1 based upon LLVM 3.4svn default target x86_64-apple-darwin13.1.0
ignoring nonexistent directory "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer /SDKs/MacOSX10.9.sdk/usr/local/include"
ignoring nonexistent directory "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer /SDKs/MacOSX10.9.sdk/Library/Frameworks"
#include "..." search starts here:
#include <...> search starts here:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/ usr/bin/../lib/clang/5.1/include
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/ usr/include
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/ SDKs/MacOSX10.9.sdk/usr/include
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/ SDKs/MacOSX10.9.sdk/System/Library/Frameworks (framework directory)
End of search list.
"/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain /usr/bin/ld" -demangle -dynamic -arch x86_64 -macosx_version_min 10.9.0 -syslibroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/ SDKs/MacOSX10.9.sdk -o hello /var/folders/zf/d5vqmmtn5mq7h6766jtlkrvr0000gn/T/main-353995.o -lSystem /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/ usr/bin/../lib/clang/5.1/lib/darwin/libclang_rt.osx.a
xew ~/$:

Adapter module:: JAR file in the build path of EJB project

Hi Experts,
I have created one adapter module, for this I have created one EJB project and also associated one EAR project to that.
I have completed my coding and changes in the xml files.
I have followed this -
http://www.sdn.sap.com/irj/scn/index;jsessionid=(J2EE3417500)ID1494558950DB01504425675464955468End?rid=/library/uuid/c0b39e65-981e-2b10-1c9c-fc3f8e6747fa&overridelayout=true
while creating the module.
but after finishing this , I can not see the ejb.jar file corresponding to the ejb project, I can see the class file generated in the build path.
but I can not see the ejb.jar in the EJB project after build.
When I checked the EAR project I found under Deployment descriptor there is a folder called module and there is a jar file named as -
EJB<my ejb project name>.jar
when I am about to deploy this EAR in the server it is showing me to choose the file from EAR project and this EAR project contain the EJB Project .
Request you to please let me know is everything ok with my project ? or please let me know how can I see the ejb.jar file corresponding to the ejb project below the build path.
Thanks
Vinny

Hi Experts,
I have created one adapter module, for this I have created one EJB project and also associated one EAR project to that.
I have completed my coding and changes in the xml files.
I have followed this -
http://www.sdn.sap.com/irj/scn/index;jsessionid=(J2EE3417500)ID1494558950DB01504425675464955468End?rid=/library/uuid/c0b39e65-981e-2b10-1c9c-fc3f8e6747fa&overridelayout=true
while creating the module.
but after finishing this , I can not see the ejb.jar file corresponding to the ejb project, I can see the class file generated in the build path.
but I can not see the ejb.jar in the EJB project after build.
When I checked the EAR project I found under Deployment descriptor there is a folder called module and there is a jar file named as -
EJB<my ejb project name>.jar
when I am about to deploy this EAR in the server it is showing me to choose the file from EAR project and this EAR project contain the EJB Project .
Request you to please let me know is everything ok with my project ? or please let me know how can I see the ejb.jar file corresponding to the ejb project below the build path.
Thanks
Vinny

[svn:fx-trunk] 12087: Dev only. Checking in Flash Builder 4 " Library Projects" for building Flex SDK SWCs in trunk.

Revision: 12087
Revision: 12087
Author:   [email protected]
Date:     2009-11-21 20:56:09 -0800 (Sat, 21 Nov 2009)
Log Message:
Dev only. Checking in Flash Builder 4 "Library Projects" for building Flex SDK SWCs in trunk. These projects are easier to import and do not require linked resource variables to be specified.
Note: although the trunk does not build textLayout.swc, there appears to be a legitimate compiler error in FlowGroupElement.as as a cast is missing. I'll follow up with TLF.
QE notes: N/A
Doc notes: N/A
Bugs: N/A
Reviewer: N/A
Tests run: N/A
Is noteworthy for integration: No
Modified Paths:
    flex/sdk/trunk/build.xml
Added Paths:
    flex/sdk/trunk/frameworks/projects/airframework/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/airframework/.flexLibProperties
    flex/sdk/trunk/frameworks/projects/airframework/.project
    flex/sdk/trunk/frameworks/projects/airframework/.settings/
    flex/sdk/trunk/frameworks/projects/airframework/.settings/org.eclipse.core.resources.pref s
    flex/sdk/trunk/frameworks/projects/airspark/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/airspark/.flexLibProperties
    flex/sdk/trunk/frameworks/projects/airspark/.project
    flex/sdk/trunk/frameworks/projects/airspark/.settings/
    flex/sdk/trunk/frameworks/projects/airspark/.settings/org.eclipse.core.resources.prefs
    flex/sdk/trunk/frameworks/projects/flex/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/flex/.flexLibProperties
    flex/sdk/trunk/frameworks/projects/flex/.project
    flex/sdk/trunk/frameworks/projects/flex/.settings/
    flex/sdk/trunk/frameworks/projects/flex/.settings/org.eclipse.core.resources.prefs
    flex/sdk/trunk/frameworks/projects/framework/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/framework/.flexLibProperties
    flex/sdk/trunk/frameworks/projects/framework/.project
    flex/sdk/trunk/frameworks/projects/framework/.settings/
    flex/sdk/trunk/frameworks/projects/framework/.settings/org.eclipse.core.resources.prefs
    flex/sdk/trunk/frameworks/projects/halo/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/halo/.flexLibProperties
    flex/sdk/trunk/frameworks/projects/halo/.project
    flex/sdk/trunk/frameworks/projects/halo/.settings/
    flex/sdk/trunk/frameworks/projects/halo/.settings/org.eclipse.core.resources.prefs
    flex/sdk/trunk/frameworks/projects/osmf/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/osmf/.flexLibProperties
    flex/sdk/trunk/frameworks/projects/osmf/.project
    flex/sdk/trunk/frameworks/projects/osmf/.settings/
    flex/sdk/trunk/frameworks/projects/osmf/.settings/org.eclipse.core.resources.prefs
    flex/sdk/trunk/frameworks/projects/rpc/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/rpc/.flexLibProperties
    flex/sdk/trunk/frameworks/projects/rpc/.project
    flex/sdk/trunk/frameworks/projects/rpc/.settings/
    flex/sdk/trunk/frameworks/projects/rpc/.settings/org.eclipse.core.resources.prefs
    flex/sdk/trunk/frameworks/projects/spark/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/spark/.flexLibProperties
    flex/sdk/trunk/frameworks/projects/spark/.project
    flex/sdk/trunk/frameworks/projects/spark/.settings/
    flex/sdk/trunk/frameworks/projects/spark/.settings/org.eclipse.core.resources.prefs
    flex/sdk/trunk/frameworks/projects/sparkskins/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/sparkskins/.flexLibProperties
    flex/sdk/trunk/frameworks/projects/sparkskins/.project
    flex/sdk/trunk/frameworks/projects/sparkskins/.settings/
    flex/sdk/trunk/frameworks/projects/sparkskins/.settings/org.eclipse.core.resources.prefs
    flex/sdk/trunk/frameworks/projects/textLayout/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/textLayout/.flexLibProperties
    flex/sdk/trunk/frameworks/projects/textLayout/.project
    flex/sdk/trunk/frameworks/projects/textLayout/.settings/
    flex/sdk/trunk/frameworks/projects/textLayout/.settings/org.eclipse.core.resources.prefs
    flex/sdk/trunk/frameworks/projects/wireframe/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/wireframe/.flexLibProperties
    flex/sdk/trunk/frameworks/projects/wireframe/.project
    flex/sdk/trunk/frameworks/projects/wireframe/.settings/
    flex/sdk/trunk/frameworks/projects/wireframe/.settings/org.eclipse.core.resources.prefs

Status Update - don't know if this is a bug, design flaw, install problem or my misunderstanding.
I got it to work by first changing my Flex library to 4.5.0 - still didn't work with current
app and update mxml files using "2.6" for their namespace versions. But I did at least
get the popup error number 16815 - indicating an error in the update version namespace.
By leaving my application namespace version at "2.6" and changing the update version to "2.5" ... bingo!
I got my new update installed autiomatically.
Is this how it's supposed to work - or are my runtimes mixed up?
Will this work the same using the Flex 4.5.1 SDK? I'll find out shortly
Hope this helps others.

Cant specify the Java Build Path in the Web Module Project

hi,
I have a problem while specify the project dependencies in the Web Module Project.While opening the properties of the web module project i cant choose the Java Build Path.The only two options i have are design root path and web service consistency check builder.Does anybody know why its like that?do i hav to reinstall the SAP developer studio?
With regards,
Jaisamma Varghese

Hi Jaisamma,
I just tested this, and for me it works as expected, within all explorer/navigator views.
Before reinstalling NWDS, check if the project itself may have some problem. Just create a new clean web module project and right-click on the project and try to access the BuildPath properties now. If it works, try to set up your project content again within this new project. Otherwise reinstalling NWDS may help.
Hope it helps
Detlev
PS: Please consider rewarding points for helpful answers on SDN. Thanks in advance!

Signed applet : problem signing jar files that are in build path

Hello,
I have a problem while trying to create an ftp applet.
I use org.apache.commons.net.ftp and i build path for commons-net-1.1.4.jar and then i build my classes.
When i create a jar file with my classes and after signing it, it works under eclipse but not on a web page.
I had signed commons-net-1.1.4.jar before to build the path in eclipse but commons-net-1.1.4.jar is not in my jar file.
What is the way to sign applet correctly even if some jar ressources are in eclipse build path.
Thank you

You were right!!!
I'm not sure what to write down in the formsweb.cfg (configuration file) , following the instructions on the on-line help of Developer Forms 10g , in step 9..
The step 9 says...
Because in this release the JACOB code is in an external Jar file and not incorporated into frmwebutil.jar, it needs to be downloaded. To do this, change the WebUtilArchive setting to read: webUtilArchive=/forms/webutil/frmwebutil.jar,/forms/webutil/jacob.jar
The doudt is pointed to the fact that the frmwebutil.jar isn't in the ORACLE_HOME\forms\webutil path but it is ORACLE_HOME\forms\java path.
Also , these paths referenced in webUtilArchive are physical paths in a Unix system or they are logical paths in a url?
Simon

Flex Build Path: fiber.swc, playerfds.swc & dcradSwcs automatically added after I removed them

Hi,
I'm working on an application which uses old Flex 3.4 (used for Adobe LiveCycle). This SDK already contains fiber.swc and playerfds.swc so I removed them from Flex Build Path. But if I reopen the project, the removed lines are there again.
So whats wrong? Bug? This is a serious issue for me since some classes from newer fiber.swc is not backwards compatible to version 3.4.
I'm using Flash Builder Premium 4.7. It would be great if I could solve that because I have to remove these paths everytime I open the project.
cu Floh

Few things I've discovered that might be able to help you.
Make sure you download both the newest version of the playerglobal.swc (for flash player 10.1), and replace it either in your SDK files, or have it in a library (in Flex 3 you need to disable the older playerglobal, I'm not sure about FB 4)
Use the newest OSMF.swc available from the OSMF downloads page.
Make sure you have the compile settings for OSMF set up in your compile line (mangle for FB4 if needed):-define CONFIG::LOGGING false -define CONFIG::DEBUG false -define CONFIG::FLASH_10_1 true
I've been able to compile flex projects using OSMF doing these steps.
Hope this helps.
-Will

Third Party Modules (Library | Develop etc.)

Besides the ability for developers to build plugin extensions (the ones with the .lrplugin extension which are widely called modules as well and reside in a module directory unfortunately), I would like to see the possibility to have third party modules that extend the currently builtin Library | Develop | Slideshow | Print | Web panes. Things that I could imagine (either being implemented by Adobe or a third party):
A Photomerge module (for creating panoramic images as in Photoshop)
A HDR module (again, as in Photoshop)
A GEO module that lets you geotag photos (from a tracklog or by dropping on a map), that displays a little map with the track and picture locations (yes, I am talking Aperture here)
Alternative publishing modules (Photobook, Web)
And many more...
There would be several benefits in my opinion:
Some of the outlined functionality does not fit very good into one of the existing modules, requires a different screen layout then offered, or is very specific and would hence justify its own module
Functionality that seems not a top priotity to Adobe but requested by enough users could be implemented by a third party (geotagging for examle)
By offering more modules with selective disabling of whole modules, different customers with different needs can shape their optimal environment. No more discussions whether this and that is a pro or a cosumer feature and should be part of Lightroom. Let third parties develop a face recognition module if someone sees a market for it. Let the pros ignore it and the consumers happily enable it. Let those people diable the builtin Web module that do not need it because they do not wnat or have a simpleviewer flash site.
Adobe can offer different versions of Lightroom (as done with other software) or sell addon module seperately.
Just a thought...

mathmeye wrote:
Just a thought...
And a very good thought indeed, me-thinks...
Many of us plugin writers are chomping at the bit for tighter integration with Lightroom.
As it stands, there's a pretty big wall between plugins and Lightroom proper (e.g. they have to be contained in modal dialogs (those that blink if you try and do anything with Lightroom before dismissing the dialog) with limited interface to Lightroom...)
Although I can imagine the challenges in exposing more of Lightroom's guts to plugins, I hope Adobe sees to move in that direction.
+1 vote...
Rob

WSDC, build path, and a dirty wsanttasks.jar

I'm attempting to use some customized Ant tasks for starting/stopping applications in Websphere Development Studio Client 5.1. I added the following line to my build.xml file...<taskdef name="wsStopApplication" classname="com.ibm.websphere.ant.tasks.StopApplication"/>...assuming that such a class might already be supported in the WS environment. Silly me - WS told me it couldn't find that class. So, I dug around and found the wsanttasks.jar buried deep in the bowels of the WS install directory. I dutifully added this JAR to the Ant properties, but got the same result. I added the JAR to the project build path, but still no custom-task love.
I've checked and re-checked the spelling. I've rebuilt the project. I've shut down and restarted WDSC. The project seems to not even recognize that it has access to the wsanttasks.jar. I was able to compile a class outside WDSC using a class from this JAR.
I'm open to suggestions as to what I might be missing.
Thanks,
§

google search:
http://p2p.wrox.com/topic.asp?TOPIC_ID=4606
I had the same problem, so I can help you on that.
You need to include 2 jar files into a class path for the wsadmin.
1) in C:\Program Files\WebSphere\AppServer\bin there is a file called setupCmdLine.bat
2) edit it and chenge the line
SET WAS_CLASSPATH=%WAS_HOME%/properties;%WAS_HOME%/lib/bootstrap.jar;%WAS_HOME%/lib/j2ee.jar;%WAS_HOME%/lib/lmproxy.jar;C:/Program Files/WebSphere/AppServer/java/jre/lib/ext/mail.jar;C:/Program Files/WebSphere/AppServer/java/jre/lib/ext/log.jar
so that includes the MAIL.JAR and LOG.JAR.
Dunno if this is same as your problem or not.

Java build path as appose to j2ee depenencies ?

if i understand right j2ee depen. basicly means one is in another's build path and has to be deployed under the same war ?
another thing , if i placed one java application in a j2ee project build path why do i have put the same jar in both of 'em ? wil it be deployed twice ?

after copy&paste the missing entries from a .classpath-file of a local project to my NWDI-based projects .classpath file, the build errors are gone.
but how to do that automatically?
and still errors occur in the develop-config perspective:
<i>ERROR: failed to resolve reference "sap.com/tc/..." for DC "....":Cannot find compartment of used component: sap.com:tc/wdp/metamodel/content</i>
kr, achim

Stubborn Build Path errors

I created a new Java project in Eclipse from an existing folder. I am getting errors like -
Unbound classpath variable: 'JRE_LIB_CORE' in project 'RFT'
Unbound classpath variable: 'JRE_LIB_GRAPHICS' in project 'RFT'
Unbound classpath variable: 'JRE_LIB_SERVER' in project 'RFT'
Unbound classpath variable: 'RATIONAL_FT_LIB' in project 'RFT' (I am using Rational Functional Tester API)
I tried removing these entries from Project Properties -> Java Build Path -> Libraries, and as a replacement, added JRE System Library. When I save these settings, the errors do not go away. And when I check project properties again, all my changes have been reverted back - the variables I had removed are back.
Can someone help?
Thanks

Best I can suggest is that that is entirely an eclispe problem.
So at a minimum it should be phrased that way (subject) and an eclipse forum would be the best place to ask.

Xcode4.1 build path (Library/Developer/Xcode/DerivedData)

Similar Messages

Maybe you are looking for