My destination was Hyderabad this time. Never been there before but I have been to India before. I really like india, nice people, beautiful country. The country is big (certainly compared to the Netherlands…) and the amount of people is huge (1.3 Billion!)
The traffic is just amazing. In Europe we mostly drive on the right side of the road, in the UK they drive on the left side and in India they drive wherever there is place…
The first time i was in India I was picked up at the airport in Mumbai (Bombay) for a taxi-drive to Pune, a 160 kilometer drive that too almost 4 hours.
The first half hour I spent saying goodbye to my life. I was pretty sure I would not survive the drive. After a while, however, you figure out the (actually very simple) rules of driving in India.
- What’s behind you is not important. It’s their problem, not yours.
- Honk at least once a minute. (Otherwise your car will explode, I think)
- use every free space on the road.
- use all available room next to a road as well.
- You have priority if you are there first.
- don’t be aggressive or mad, the others know what they are doing.
That’s about it. The last one is important. Most drivers know pretty well what they are doing. “But India has the highest mortality rate in traffic” i hear you say. Yes true. But that happens only outside of the city. In the city you just cannot drive fast enough to die in an accident.
In the same way you can cross the very busy streets. Have confidence in the others, they will see you and decide which side they will pass you. So just cross the street and don’t hesitate.
The main reason I really like to go to india is the food. Indian food is really awesome. Spicy and very different from our european food. I found out that Hyderabad is famous for its Biryani and that they eat spicier than in the rest of India.
I don’t mind, i’m used to eating quite spicy.
In India they also eat in a special way: with the hand. Only the right hand, the other hand is used for “other purposes” (Do the math…) That is a bit difficult being a lefty but I managed. Yes I ate with my hands as well. When in Rome, do as the Romans.
I learned that the system of “Generate Code, Generate RXF files, Deploy, switch to IDE, compile” is still difficult for people to understand.
if you follow the IBM way of creating an adapter for Rhapsody, you generate code in Rhapsody, that will also generate a makefile and you build from Rhapsody. As already said, we decided to do this differently because:
- command-line length in Windows. Large Applications cannot be built like this
- too many settings and extra files you need for embedded targets
So we use a different approach.
Still generates Code from the Rhapsody model
Does not really build but generates the RXF include files that provide the static settings for e.g. the Memory Blocks etc.
Depending on the version of the RXF, we have called deploy in the “run” phase but now we call that mostly in the “Build” phase.
It takes your Rhapsody generated sources (And the RXF includes _and_ the complete RXF and inserts them in a prepared IDE project.
- Switch to your IDE
Windows TAB, your IDE will probably show you that files have changed
Use your IDE to compile. And Debug.
What you lose in this way is the roundtripping, unless… you select the Rhapsody Generated Source Directory as Home for your IDE Project.
- using Tools, <RXF> Deployer Configuration only configures the deployer. It does NOT deploy!
- You have to prepare your IDE project. We deliver the “Getting Started” project (And a backup) that works. Your own project must include some things like “RXF” and “Generated Source” Folders. Check your Documentation.
- If you have made changes to your IDE project: SAVE!!!! Deploy will use the IDE settings on the disk and will also overwrite your changes…
- Clean up your old Rhapsody sources in Rhapsody (Code, Clear Redundant Source Files) to prevent them from being deployed.
I hope this helps you in understanding the RXF!
Back to India
OK, that’s it, have fun with Rhapsody and the RXF!
Walter van der Heiden (firstname.lastname@example.org)